Details
-
Bug
-
Resolution: Done
-
Major
-
1.2.0.CR1
-
None
-
None
Description
I have a big problem here because of bearer token size.
I'm using keycloak within a SaaS application, so I need create alot of realms.
After 20 realms created, the bearer token issued for master admin user has more than 8kb.
It's huge for a single header and Apache limits headers upto 8kb.
With 1000 realms, the bearer token of master admin user will have 400kb.
It'll be impossible to use keycloak in production, it occurs because "resource_access" property has all realms with all possible roles.
I think we can prevent that problem not issuing "resource_access" to a user with "admin" role in master realm.
Another approach is storing "resource_access" state in the server side, which will improve network performance alot.
Attachments
Issue Links
- is duplicated by
-
KEYCLOAK-3067 Size of a request header field exceeds server limit
-
- Closed
-
-
KEYCLOAK-3442 whoami and bearer token
-
- Closed
-
- relates to
-
KEYCLOAK-4593 Support having large number of realms
-
- Plan
-