Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide limited redirect support for OIDC Web client when auto-redirect is disabled #43937

Closed
sberyozkin opened this issue Oct 17, 2024 · 1 comment · Fixed by #43938
Closed
Labels
area/oidc kind/enhancement New feature or request
Milestone

Comments

@sberyozkin
Copy link
Member

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

@sberyozkin sberyozkin added the kind/enhancement New feature or request label Oct 17, 2024
Copy link

quarkus-bot bot commented Oct 17, 2024

/cc @pedroigor (oidc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/oidc kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant