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
Hi,
First, I want to thank everyone working on this project for their efforts.
I’m using @fastify/passport, @fastify/secure-session, and openid-client in my application. When users log in via Keycloak, the tokens returned (e.g., id_token) are encrypted using secure-session and stored as cookies in the user's browser.
The issue arises when I redirect users from my application to Keycloak's Account Management Console to update their profile or verify their email. Since the tokens are encrypted in the session, Keycloak cannot access the id_token to identify the user, and the user is prompted to log in again.
Is there a way to securely share the encryption secret used by secure-session with Keycloak so that it can decrypt the tokens and allow the user to proceed without logging in again? Or is there another recommended approach to handle this scenario?
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.
Hi,
First, I want to thank everyone working on this project for their efforts.
I’m using
@fastify/passport,@fastify/secure-session, andopenid-clientin my application. When users log in via Keycloak, the tokens returned (e.g.,id_token) are encrypted usingsecure-sessionand stored as cookies in the user's browser.The issue arises when I redirect users from my application to Keycloak's Account Management Console to update their profile or verify their email. Since the tokens are encrypted in the session, Keycloak cannot access the
id_tokento identify the user, and the user is prompted to log in again.Is there a way to securely share the encryption secret used by
secure-sessionwith Keycloak so that it can decrypt the tokens and allow the user to proceed without logging in again? Or is there another recommended approach to handle this scenario?Thank you!
All reactions