Closed
Description
Before reporting an issue
- I have searched existing issues
- I have reproduced the issue with the latest release
Area
admin/ui
Describe the bug
I have such groups:
- global_ldap
- office
- global_local
- office
Members, synced from LDAP, of the group /global_ldap/office
also appear as members of the local Keycloak DB group /global_local/office
Version
21.0.2
Expected behavior
Members of those two groups, with unique paths, but the same names. should be unique.
E.g.:
Groups:
- "global_ldap"
- "office", Members: John, George
- "global_local"
- "office", Members: < none >
Actual behavior
Groups:
- "global_ldap"
- "office", Members: John, George
- "global_local"
- "office", Members: John, George
How to Reproduce?
- Create a mapper for LDAP group, import group - for example,
/global_ldap/office
- Create new Keycloak local group in some different group path, that is also called
office
- for example/global_local/office
- Check members of the local group
/global_local/office
, normally there should be none, but you will see members of LDAP group/global_ldap/office
Anything else?
It only happens when LDAP group is involved, local (keycloak's) groups with the same names, but different paths, do not have this issue.
Activity