We were using OpenID + Keycloak for signing in and out, it was working perfectly in 10.9.1. However, after upgrading the portal to 11.1, we are having an issue as follows:
- Open portal, Sign-in to portal (>> signed in successfully)
- Open portal again in new browser tab same session (here is the issue)
- Expected: user should be logged in automatically because he/she logged in already in the same session.
- Actually: portal loads the landing page with Sign in button as if user is not logged in. However, when user click on Sign in and select the option to login via Keycloak, page is redirected directly to portal and user is signed in without entering username/password.
We have tried to trace what's going on from the browser developer tools, I believe that there is no authentication token stored in the cookies after the initial login because the problem happens when user open new tab and load portal page, and it found no auth cookie = not signed-in. However, when user click on sign in and start communication with Keycloak, Keycloak redirects it directly to portal with no action needed from the user cause the initial auth token is stored on keycloak server side already.