You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, when quarkus-oidc (or other OIDC extension) calls OIDC provider endpoints like the discovery one, the OIDC provider will send a redirect request to the same discovery endpoint but with some cookies.
Quarkus OIDC uses Vert.x WebClient. As far as managing redirects is concerned, WebClient follows redirects by default, with some addition work required at the Vert.x level to deal with such redirects.
If the auto-redirect is disabled, then Quarkus OIDC should allow a single, same URI redirect, only if the cookies are available. Essentially it is a single safe retry case in case of the redirect since the request does not follow a new URI.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered:
Description
Sometimes, when
quarkus-oidc
(or other OIDC extension) calls OIDC provider endpoints like the discovery one, the OIDC provider will send a redirect request to the same discovery endpoint but with some cookies.Quarkus OIDC uses Vert.x WebClient. As far as managing redirects is concerned, WebClient follows redirects by default, with some addition work required at the Vert.x level to deal with such redirects.
If the auto-redirect is disabled, then Quarkus OIDC should allow a single, same URI redirect, only if the cookies are available. Essentially it is a single safe retry case in case of the redirect since the request does not follow a new URI.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: