Skip to content

Support JWT bearer client authentication for quarkus-oidc #40013

Open

Description

Description

Sometimes, OIDC clients are expected to authenticate using an out of band, so called JWT bearer token, provided, for example, in Kubernetes or some shared secured file folder. Furthermore these tokens can be dynamic, so they can't configured in properties.
#38541 made it possible to easily pick up such tokens from custom OIDC client filters.

However, quarkus-oidc does not support this case yet.

Implementation ideas

May be OidcRequestFilter can be used to augment the request by setting a property on OidcRequestContextProperties, exactly as it can be done on RoutingContext.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions