Repository navigation
STORE ACCESS-TOKEN BY USER ON DB #19064
Replies: 2 comments 4 replies
|
[This statement was not factually correct, so it was removed to not confuse more users] |
|
thank you for the quick reply. Yes, I'm trying to configure the db directly from the cache configuration, but at the moment I'm getting the following error: Caused by: java.util.concurrent.ExecutionException: org.infinispan.commons.CacheConfigurationException: ISPN000327: |
|
Why exactly would you want Keycloak to store the Tokens it emits? |
|
it's needed in my organization for a security reasons. |
|
Depending on configuration, Keycloak creates a lot of potentially short-lived tokens and storing them all might create a huge pile of data. Not sure what security requirement exactly you can fulfil by storing them. Also, AFAIK they are also not stored currently, not even in memory. At least I don't see a |
|
I was indeed thinking of |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone! It would be of interest for me to solve a problem: when I access keycloak from the interface, an access-token is issued to the user (on /token). The question I ask myself is: is there a way to be able to go and persist this data on the db (I use a mysql)? because going to see the various tables that are automatically saved on the db by keycloak, I don't see this access-token saved in any!! thank you all in advance everyone.
All reactions