Hmm, I don't know enough to give you a confident answer yet. The information provided in the extracts does not specify the exact endpoint to be used for the

remote_json

authorizer in Ory Network. However, it's mentioned that the

remote_json

authorizer makes a HTTP POST request to a remote endpoint with a JSON body. If the endpoint returns a "200 OK" response code, the access is allowed, if it returns a "403 Forbidden" response code, the access is denied. You may want to check the Ory documentation or the Ory Network's API documentation for more specific details on the correct endpoint to use. Here are some useful links: - [Ory Oathkeeper Documentation](https://www.ory.sh/docs/oathkeeper/) - [Ory Network API Documentation](https://www.ory.sh/docs/ecosystem/projects#ory-oathkeeper)

Based on the information provided in the extracts, there isn't a specific guide on how to authenticate a self-hosted Oathkeeper to call Ory Network endpoints. However, Ory Oathkeeper uses authenticators to verify the identity of the client making the request. For example, in one of the extracts, a configuration of Ory Oathkeeper uses the [cookie authenticator](https://www.ory.sh/docs/oathkeeper/pipeline/authn#cookie_session) against Ory Kratos and proxies only authenticated requests to

<http://ws:8080>

upstream.

yaml authenticators:    - handler: cookie_session

This suggests that you might need to use an appropriate authenticator to authenticate your self-hosted Oathkeeper with the Ory Network. The choice of authenticator would depend on the authentication method used by the Ory Network. For more detailed information, you may want to refer to the [Ory Oathkeeper documentation](https://www.ory.sh/docs/oathkeeper/) or reach out to the Ory community for support. If you require professional support, Ory offers dedicated [support plans](https://www.ory.sh/support/) for self-hosting organizations.