Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Not certain if this helps with said error, but you should tell oathkeeper the port of the upstream
``` "url": "<http://auth:8000>"```
What URL are you firing postman against?

Hey <@U02GX5SET4Y> thanks for replying! I am using <http://127.0.0.1:4455/secret|http://127.0.0.1:4455/secret>

Hey <@U02GX5SET4Y> thank you! I have made it by using your url! 

When using docker, 127.0.0.1 refers to the container itself, not to the host system ;)

Just curious if I using kubernetes with Oathkeeper, am I able to expose it as a reverse proxy without any service like <http://ambassador.IO|ambassador.IO> or Istio or traefik in front?

Latest article I can find is from 
<https://github.com/ory/oathkeeper/issues/263|https://github.com/ory/oathkeeper/issues/263>

<https://blog.getambassador.io/part-2-api-access-control-and-authentication-with-kubernetes-ambassador-and-ory-oathkeeper-q-a-127fa57f6332|https://blog.getambassador.io/part-2-api-access-control-and-authentication-with-kubernetes-ambassador-and-ory-oathkeeper-q-a-127fa57f6332>