Repository navigation
Refresh Token Algorithm
#19893
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bold
Uh oh!
There was an error while loading. Please reload this page.
I've been trying to change the default algorithm for refresh tokens in my Keycloak instance from HS256 to my preferred algorithm, ES512 I want this to be the forced algorithm. I updated the default algorithm under tokens within realm management accordingly, but it seems that the refresh tokens are still being generated with the old algorithm, even after removing the keys, they get brought back under the fallback-hs256 name. I can force the other tokens by modifying the clients, but there is no option for refresh tokens.
Has anyone encountered this issue before? How can I make sure that the refresh tokens are signed using the new algorithm? Any advice or suggestions would be greatly appreciated. Thanks in advance!
All reactions