You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SECURITY: KEYCLAK_SESSION and KEYCLOAK_SESSION_LEGACY
#15447
2 cookies are not having httpOnly flag:
KEYCLAK_SESSION and KEYCLOAK_SESSION_LEGACY
If the cookies contain session ID they shall have httpOnly flag as the session ID is a sensitive data.
I found some old Q&A on that here: https://lists.jboss.org/pipermail/keycloak-user/2017-September/011888.html
While it says: it is used for determining if the user is still logged in, it does not say what cookie contains and if there is a justification for not having HttpOnly. Is the answer really valid one?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Maybe an oldie but not well explained.
2 cookies are not having httpOnly flag:
KEYCLAK_SESSION and KEYCLOAK_SESSION_LEGACY
If the cookies contain session ID they shall have httpOnly flag as the session ID is a sensitive data.
I found some old Q&A on that here:
https://lists.jboss.org/pipermail/keycloak-user/2017-September/011888.html
While it says: it is used for determining if the user is still logged in, it does not say what cookie contains and if there is a justification for not having HttpOnly. Is the answer really valid one?
in fact we dont want javascript to access cookies at all if they contain sensitive information.
https://owasp.org/www-community/HttpOnly
All reactions