Repository navigation
Much bigger bearer token for admin console after upgrading to Keycloak 26 #37406
Unanswered
natan-abolafya
asked this question in
Q&A
Replies: 1 comment 1 reply
|
This is strange. Enabling lightweight access token on the
|
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I don't understand some parts of keycloak so I need some guidance.
After we've upgraded from 25.0.6 to 26.1.0 (and then 26.1.2), the admin console was spinning indefinitely after login. After some investigation we've found out that the bearer token is much bigger (~45kb) than it used to be and hits AWS load balancer header size limit, so it kept returning HTTP 400.
Digging into the bearer token, I saw that the JWT had now
resource_accessclaim (and some others such asaud,realm_access) with lots of access privilege information in it. Looking at the Keycloak 25 deployment, it did not haveresource_accessclaim, so it is smaller. I have corelated that to this release info“Full Scope Allowed” are now enabled on these two clientsand disabled that feature onsecurity-admin-consoleclient.Now the extra claims are gone and the token is smaller again. However all API calls now get HTTP 403 and all I could see on the console is "HTTP 403 Forbidden".
When I try to reproduce this on my own local keycloak deployment, I can't make it include these claims even when the
Full Scope Allowedis enabled. So perhaps there is a config that is enabled on the deployment I'm having problem with that triggers this. Any idea what config that could be? As I can't login to the console, it's a bit hard to check.All reactions