![]() ![]() I also searched for ways to identify if the browser is running on incognito mode, but all I found on stack exchange does not work nowadays, probably because the engine can really hide it from the web pages. And next time you launch the browser from its regular shortcut, you must select which profile to use :( It stores nothing on history, but because it the guest aka "very barebones" profile, it has no support for addons etc. As a workaround, I once used the guest profile like so I have tried it on a lot of chromium based browsers (chromium and chrome on windows and linux, brave and opera on linux only) and the result is always the same. And that is the same problem I have with my -app approach above, the -incognito part seems to be ignored. But I’m already using Keycloak 12.0.I just made one, for facebook! I am on linux, so the relevant line looks like soīrave-browser -profile-directory=Default -app-id=(string)Īdding -incognito seems to have no effect, because I can see the extra entries created in brave://history. I think it’s something related to the SameSite and HttpOnly in the headers. The only thing I couldn’t I understand why chrome blocks some Keycloak cookies. Also, the silent refresh iframe worked perfectly. When I changed my front-end domain to be the app worked perfectly and the cookies weren’t blocked.My app considered Keycloak cookies as Third-party ones. So, my front-end was at and Keycloak was at. The cookies problem and the session change were because of deploying my front-end on a different domain. ![]() The callback had a code that performs a logout function hence the login session terminates immediately. The front-end then fires the callback.When chrome blocks the cookies the session keeps changing for some reason which is related to blocking the cookies. ![]() When I open the front-end in the Incognito mode chrome blocks some cookies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |