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

Hi all - tiny question, maybe :slightly_smiling_face: I’d like to migrate an existing API implementation that uses an opaque API key in a header like so: `Authorization: apikey XXXXXXXXXXXXX`. Can I migrate in Oathkeeper to detect those API keys based on that auth scheme of `apikey`, or will I have to convert my clients’ code to put `bearer` instead?

I guess you are talking about the bearer token authenticator? <https://www.ory.sh/docs/oathkeeper/pipeline/authn#bearer_token>
according to docs, the request is forwarded including all headers, so only the downstream session store has to know what token to use

You can use a hydrator to validate and populate the request