Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error handlers & matches not supported #41

Closed
piotrmsc opened this issue Jul 1, 2020 · 3 comments
Closed

Error handlers & matches not supported #41

piotrmsc opened this issue Jul 1, 2020 · 3 comments
Labels
stale Feedback from one or more authors is required to proceed.

Comments

@piotrmsc
Copy link
Collaborator

piotrmsc commented Jul 1, 2020

Description

Oathkeeper supports error handlers with for example redirect. This property is not supported in the controller but for some users this feature is desired. The same goes with error matches

Rule Spec does not have those properties https://github.com/ory/oathkeeper-maester/blob/master/api/v1alpha1/rule_types.go#L59 and CRD needs to be updated as well.

@aeneasr
Copy link
Member

aeneasr commented Jul 1, 2020

Nice! Please keep in mind that we want to refactor the config a bit...

ory/oathkeeper#441

@zd9KgA
Copy link

zd9KgA commented Nov 2, 2021

Is there a workaround as long as error handlers are not supported (other than resorting to a configuration at the global level)?

@github-actions
Copy link

github-actions bot commented Nov 3, 2022

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Nov 3, 2022
@github-actions github-actions bot closed this as completed Dec 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Feedback from one or more authors is required to proceed.
Projects
None yet
Development

No branches or pull requests

3 participants