OIDC CodeAuthenticationMechanism does not work if the proactive authentication is disabled
See original GitHub issueDescribe the bug
Adding quarkus.http.auth.proactive=false
breaks the OIDC adapter code flow (ex, adding this property to integration-tests/oidc-code-flow/..../application.properties
breaks the tests)
Reported originally at https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/OIDC.20BearerAuthenticationMechanism.20for.20unproteced.20resources
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
OpenID Connect (OIDC) authorization code flow mechanism
The Authorization Code Flow mechanism authenticates users of your web application by redirecting them to an OIDC provider, such as Keycloak, to log...
Read more >How to access JWT in Quarkus when proactive auth is disabled?
I see 2 distinct problems in informations you added : You got to validate token (if proactive auth is disabled); You got to...
Read more >OpenID Connect authentication | Elasticsearch Guide [8.5]
It is specifically designed to support authentication via an interactive web browser, so it does not operate as a standard authentication realm. Instead,...
Read more >quarkusio/quarkus 1.9.0.CR1 on GitHub - NewReleases.io
... #12090 - OIDC CodeAuthenticationMechanism does not work if the proactive authentication is disabled; #12076 - AdditionalBeanBuildItem - clarify javadoc ...
Read more >How-to: Setup OIDC Authentication in Amundsen - Stemma
Please note that only setting up OIDC: does not enable User Profiles in Amundsen UI. does not ingest users in your database. If...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Created a new issue https://github.com/quarkusio/quarkus/issues/12882
@sberyozkin I just tried the fix with Quarkus-1.9.0.Final. It works for the flow and the REST endpoints but breaks my unit-tests which are using the
@TestSecurity(user = "harald")
annotation.SecurityContext.getUserPrincipal()
returns null.My current workaround is
%test.quarkus.http.auth.proactive=true
but I don’t like it.