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

Hello :wave:  has anyone encountered this and have a possible fix ? <https://github.com/ory/oathkeeper/issues/878>

i’m not sure if this is the problem, i but i think you’ll need to move bearer_token above noop, otherwise i don’t think it will ever execute that authenticator as the noop one will always pass

why would the order in the config matter ? in the rules you just assign what authenticator you want, there would the order matter

ah, ignore me, i thought that was in a rule, i missed that you were talking about the top-level configuration