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
Logout does not work as expected #756
Comments
After logging out, it appears that I'm still legged in. Going to I thought that is was caused by 8356517, but reverting that commit didn't fix the problem. |
Note:
|
## [1.59.8](v1.59.7...v1.59.8) (2023-12-29) ### Bug Fixes * **auth:** logout local session after auth0 logout ([6e7299d](6e7299d)), closes [#756](#756) * comments ([21c0f23](21c0f23)) * **env:** no need to expose local db, assuming that users were uploaded to auth0 "dev" tenant's db ([31b1019](31b1019)) * **env:** typo on required env var: `AUTH0_CLIENT_SECRET` ([eb54506](eb54506)) * **makefile:** `docker-seed` to start services ([998607b](998607b)) * **makefile:** `make dev` to start openwhyd against "dev" auth0 tenant ([4a1ae82](4a1ae82))
Logout works as expected on localhost, against "dev" Auth0 tenant, but still not in production. |
Update: logout worked in prod after "clearing site data" of openwhyd.org, using chrome dev tools. => no more How to fix?
|
…alize alongside Auth0 contributes to #756.
## [1.59.10](v1.59.9...v1.59.10) (2023-12-29) ### Bug Fixes * **auth:** make sure that legacy auth/session middleware is not initialize alongside Auth0 ([1ada22f](1ada22f)), closes [#756](#756)
This commit also contributes to fixing this issue: 25e5e65 |
References, if the issue re-appears: |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: