larisa-patrascu opened a new issue, #41578: URL: https://github.com/apache/superset/issues/41578
### Bug description I have an application integrated with Apache Superset using Keycloak for authentication (SSO). The flow is the following: 1. User logs into my application via Keycloak 2. Application redirects to Superset 3. Superset logs the user in automatically (SSO) and redirects to dashboards 4. User closes Superset tab and returns to my application 5. User logs out from my application 6. User logs in again with a different account 7. Application redirects again to Superset Actual behavior: Superset still shows the previous user session (old user), even though: - The browser is now authenticated in my app with a different Keycloak user - A new login happened in the main application Superset does not re-authenticate and reuses the existing session. Expected behavior: After logout/login with a different user in the main application: - Superset should detect the new identity - Superset should not reuse the previous session - A fresh SSO authentication should occur via Keycloak ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
