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

pac4j extension does not handle logouts/session expirations #12183

Closed
andrewm-aero opened this issue Jan 20, 2022 · 2 comments
Closed

pac4j extension does not handle logouts/session expirations #12183

andrewm-aero opened this issue Jan 20, 2022 · 2 comments

Comments

@andrewm-aero
Copy link

Affected Version

v0.22.0

Description

The pac4j extension does not gracefully handle login expirations in the unified console. The first request to the unified console HTML endpoint correctly redirects to the OIDC login page, which then correctly redirects back to the console. The plugin seems to assume that the original token will always work, and if it doesn't, will get into a loop of attempting a background request (e.g. /druid/v2/sql), which fails due to CORS, instead of redirecting the user to the login page. This breaks the functionality of the console, and can only be fixed by manually refreshing the page. This behavior is not observed with any other application we have connected to this same OIDC provide with identical configurations.

Copy link

github-actions bot commented Dec 9, 2023

This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 weeks if no further activity occurs. If this issue is still
relevant, please simply write any comment. Even if closed, you can still revive the
issue at any time or discuss it on the dev@druid.apache.org list.
Thank you for your contributions.

@github-actions github-actions bot added the stale label Dec 9, 2023
Copy link

github-actions bot commented Jan 6, 2024

This issue has been closed due to lack of activity. If you think that
is incorrect, or the issue requires additional review, you can revive the issue at
any time.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant