Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Done
-
None
-
None
-
None
Description
Currently the WildFly adapter (and others) store the tokens in the users HTTP session.
As long as the application is stateful and already uses sessions there's no problem with that. However, for applications that has been designed to be stateless (clustered without sticky sessions) that can be problematic.
We should add an option to the adapters to have them store the tokens in cookies instead of the HTTP session.
Attachments
Issue Links
- is related to
-
KEYCLOAK-742 Adapter config parameter to allow refreshing token in each request
-
- Closed
-