Hey @User I saw your comment here on Github about adding

bearer_token

to the Oathkeeper Maester config: https://github.com/ory/oathkeeper/issues/878#issuecomment-1096420048 We successfully implemented this today, but while doing so it seems that the

noop

authenticator stopped working, even though it is in the list. I updated the auth access rules that used

noop

to

anonymous

and that seemed to work fine. One other issue is that we had to use the key

envs

instead of

env

so that it looks like this:

oathkeeper-maester:
  deployment:
    envs:
      - name: authenticatorsAvailable
        value: '[noop,unauthorized,anonymous,bearer_token,cookie_session,oauth2_client_credentials,oauth2_introspection,jwt]'

All that said,

bearer_token

finally showed up in the rules without any maester errors, but I wasn't able to get

bearer_token

working while testing with Postman using the same

ory_kratos_session

as set in the cookie which does work in a browser.

Hey @User We've setup

bearer_tokens

but haven't got around to using them yet, as we're mostly using

oauth2_client_credentials

I should be testing

bearer_tokens

today/monday as I'll have finished getting Kratos setup, so can report back any findings as I'll be testing with Postman myself too

@User sounds good, thanks for the update!