Skip to content

quarkus.oidc-token-propagation-reactive.enabled-during-authentication does not work correctly in the code flow #38431

Closed
@sberyozkin

Description

Describe the bug

As reported by the user, if this property is used with the code flow, then given that both ID token and access token are TokenCredential instances, ID token is propagated, probably due to a random selection.

This is not a problem in the code flow when the token propagation is initiated with the REST Client in the endpoint - indeed we have many tests and demos confirming it - it works because AccessTokenCredential CDI producer has a higher priority than IdTokenCredential - looks like this priority is not enforced with the quarkus.oidc-token-propagation-reactive.enabled-during-authentication solution, #34933

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions