-
Notifications
You must be signed in to change notification settings - Fork 263
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
Incorrect oauth behaviour when logging out of keycloak #7382
Comments
The problem persists with version @Alfresco@4.7.0 |
why the user is not in APS? |
Hello, the user is not synchronised from ldap because he does not have the required rights but he can log in via keycloak. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behaviour:
It is not possible to log out of keycloak if an invalid user is created in acs or aps with @Alfresco@4.3.0
Expected behavior:
It should be possible to log out from keycloak even if the users in aps or acs do not exist or are invalid.
Steps to reproduce the issue:
Component name and version:
The problem occurs on 2 levels.
First Problem
The first problem occurs after the login in keycloak was successful. Then as soon as i try to load the user from bpm i get a 401 response and the session is invalidated.
alfrescoApi.ts:197
oAuth2Auth.ts:699
The local storage is cleared from all authentication settings. Therefor the logout mechanism doesn't work at all since keycloak requires the id_token to logout
oAuth2Auth.ts:673
After i disabled the invalidation of the session the id_token was not deleted and the logout to keycloak works in theory.
Unfortunately, incorrect behaviour sometimes occurs nevertheless.
Second Problem
Sometimes the logout does not work at all. This part is a bit tricky.
After calling the code in
oAuth2Auth.ts:694
the browser is (sometimes) redirected to the app with the hash fragments created for the iframe.
oAuth2Auth.ts:355
With the redirect to my app with the hash fragments i am logged in again.
So i had the situation where i could not logout from the app at all.
Browser and version:
I could not reproduce the behaviour every time - it acts like a race condition.
It seems to happen more often in firefox than in chrome and more often if the dev console is open.
Node version (for build issues):
14.15.3
The text was updated successfully, but these errors were encountered: