Add additional headers for `remote_json` authorizer

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [X] 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

Since Ory Keto is an Ory Network citizen right now and requires for additional token set to the Authorization Header, it makes it impossible to configure the remote_json authorizer against Ory Cloud Keto.

Describe your ideal solution

It would be best to have headers or something similar compared to remote authorizer to configure oathkeeper remote_json authorizer

Workarounds or alternatives

It's possible to create a simple HTTP service that proxies requests and adds Authorization header

Version

latest

Additional Context

No response

+1 having the same challenge, trying to integrate oathkeeper with OpenFGA

+1 to this!

+1 ... looks like it has been a while

And another plus one. Topaz requires Authorization and Aserto-Tenant-Id headers.