Set fallback when no rules found

[khusseini]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe your problem

When using nginx auth-url backend to make use of the Ory Oathkeeper decision API, we run into an incompatability when oathkeeper cannot find matching rules. Oathkeeper will throw a 404 when no rules were matched, however nginx does not accept 404 error codes and in turn throws a 500 to the client.

It would be amazing if we could set a fallback rule when no other rules were matched. Currently it is not possible to have a catch-all rule as such a rule would result Oathkeeper to match more than one rule for any request and in turn throw a 500 error.

Describe your ideal solution

Implement a fallback rule to match when no other rules were able to match.

Workarounds or alternatives

Currently there are no alternatives but to define a rule for every possible route in the application. This is very tedious and can quickly get out of hand for larger applications.

Version

v0.40.9

Additional Context

No response