Support working with query string and JSON body

[renom]

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.
• This issue affects my Ory Cloud project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe your problem

Support working with query string and JSON body

Describe your ideal solution

1. Mutating and hydrating query string and JSON body (e.g. adding/replacing/removing a query string parameter or a JSON body path)
2. Extracting data from query string and JSON body for keto_engine_acp_ory (e.g. data from a query string parameter or a JSON body path)
3. Support autherizer rules for query string parameters and JSON body paths (e.g. allowing or disallowing specific values)

Workarounds or alternatives

Version

Additional Context

No response

[omerlh]

Any updates on that? It seems like #843 is related to this.
We are more interesting in query params right now, will a PR will be accepted here?

[omerlh]

I found a workaround for query params:

{{ .MatchContext.URL.Query.Get \"a\" }}

No code change is requires in oathkeeper to support it, just the power of Go templates 💪

[ViswanathB]

I found a workaround for query params:

{{ .MatchContext.URL.Query.Get \"a\" }}

No code change is requires in oathkeeper to support it, just the power of Go templates muscle

Like this idea: @omerlh Did you find any issues with this at scale?

[omerlh]

Nope, this working pretty well for us

[denysandriyanov]

Have you had a chance to get the way how to extract some values from original request body?

[omerlh]

If you use the remote authorizer the full request body is sent to this service so you can use the request body for authZ. We built a small service that handle authZ so it also handles this part.

[github-actions]

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 🙏✌️