-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Comments
Nice! Please keep in mind that we want to refactor the config a bit... |
Is there a workaround as long as error handlers are not supported (other than resorting to a configuration at the global level)? |
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
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 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 🙏✌️ |
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.
The text was updated successfully, but these errors were encountered: