Re: [keycloak-dev] "You are already logged-in" issue

Discussed this with Marek a bit and may have a potential solution here. My suggestion is the following: 1. Add a timestamp to a cookie - this timestamp is updated whenever the user makes any action in the authentication session. Basically submitting any form. 2. Add a piece of JS that reads the value of this cookie. If the value changes it will refresh the page. This will hand over the logic of what to do now to the Keycloak server. If username/password was submitted on one tab, the second tab should automatically update and show the next step (or if complete redirect to the client with successful login) 3. Change the client_id param to a more generic state param. This should be a base64 encoded value with the info that we need in case root authentication session is lost (base64(c=<client-id>&r=(redirect-uri). With having a single param base64 encoded we can more easily add additional info if we need without having to add more query parameters. 4. Root authentication session should not be deleted straight away if there are more child authentication sessions, but rather it should be garbage collected after X mins of inactivity. 5. If root authentication session is garbage collected we should redirect to the client with login error, rather than display error page, with some error message stating failed due to inactivity. The client can then handle it accordingly. On Thu, 13 Jun 2019 at 14:53, Vlasta Ramik <vramik(a)redhat.com&gt; wrote: