Repository navigation
Replies: 1 comment
|
I would suggest a new entity GroupUserAttributes. This would open Keycloaks users and groups database model in a generic way where it's possible to additionally store information like
By adding such an entity to the native Keycloak model the amount of groups when storing such data in subgroups would decrease enormously and would therefore increase the query performance. Thx for opening this discussion |
0 replies
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.
We have a use case where we need to store attributes for users in groups where the user is a member (e.g., something like a membership number for a group). Currently, we solve this with subgroups that have the user's ID as their name and store the values there as group attributes. Since there will be a relatively large number of groups, this bloats the entire system and is sometimes not particularly efficient.
I would appreciate it if we could either add a group field to UserAttributes or introduce a new entity (e.g., UserGroupAttributes) that could solve the problem more elegantly.
All reactions