-
Notifications
You must be signed in to change notification settings - Fork 487
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
Bug : Setup for development environment causes re-login every 5 seconds. #1365
Comments
Here is the video recorded in this situation: zoom_1.mp4 |
That's not good. I think we need more information.
|
@mikisou 追加で情報もらえませんか? |
@EricWittmann This is my environment: There are some issues reported on the Chrome's console about SameSite attribute for a cookie. |
OK so it sounds like this is specific to Safari browser - is that right? I don't have a Mac so I can't test this myself. @Apicurio/developers - does anyone have a Mac and can try to reproduce this? |
@EricWittmann I guess this problem comes from Chrome's change of its default behaviour. As of version 80, Chrome treats Cookie SameSite=Lax by default. As you can see in the following capture, Since So, Keycloak fails to get As a result, Then, it falls into logout process in the main window. Anyway, It's all happens in Keycloak... |
I wonder if this would be resolved simply by upgrading the https://www.npmjs.com/package/keycloak-js I think the newer versions should work despite the older version of Keycloak we've got running in the cloud. |
Since It's required to upgrade Would you please check: |
Thanks for figuring this all out - much appreciated. I'll see what I can do about upgrading the auth server. |
@EricWittmann |
Darn I lost track of this activity. I don't think there is any reason to expect a new version of Keycloak to be a problem for us. We'll just have to test it! |
@EricWittmann |
I'll need to find time to upgrade studio.apicur.io's auth to KC 12. Thanks for the update. |
After following the URL below, the keycloak server now tries to re-login once every 5 seconds just by accessing it.
This is a lot of development work, so I'm working around it by setting the login retry to 86,400 seconds (it takes about 30 seconds to re-login). What can I do to solve the underlying problem?
https://www.apicur.io/studio/docs/setting-up-a-development-environment
The text was updated successfully, but these errors were encountered: