Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow ldap group mapper to flatten nested groups #28066

Open
andrewmeyer opened this issue Mar 19, 2024 · 0 comments
Open

allow ldap group mapper to flatten nested groups #28066

andrewmeyer opened this issue Mar 19, 2024 · 0 comments
Labels
kind/enhancement Categorizes a PR related to an enhancement status/triage

Comments

@andrewmeyer
Copy link

andrewmeyer commented Mar 19, 2024

Description

by default, openldap does not support nested groups the way people think it does. LDAP instead expects the software requesting the information to unpack any nested groups to create the full group list.

Dynamic groups are also not widely supported and its implementation is obtuse at best.

Ideally, the group mapper would have a toggle to "flatten" group membership in keycloak when sending them to LDAP - essentially converting nested groups into static groups. The end result of this is allowing keycloak to be a source of truth to build static ldap groupOfNames that standard applications can leverage identically to how they are applied inside of keycloak.

This should be a toggle option because it would break ldap-->keycloak group memberships. The intended use case here is to use keycloak as the frontend and feed information into LDAP so that applications that do not have feature-rich OIDC/SAML support can use LDAP for users and groups.

Discussion

No response

Motivation

While LDAP will happily store a group inside of a group, it does not behave the way one would think. LDAP does not automatically unpack nested groups when searched, it instead relies of the querying software to do the unpacking. Furthermore, many applications do not reasonably handle groups provided in the authentication token, if at all. Instead, LDAP would need to be used for centralized group management

Details

as stated, it may make sense to add this feature to the group mapper for LDAP connections. It will need to be toggleable because if the flattened groups were synchronized back to keycloak it might disrupt the permissions schema an admin has created.

@andrewmeyer andrewmeyer added kind/enhancement Categorizes a PR related to an enhancement status/triage labels Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Categorizes a PR related to an enhancement status/triage
Projects
None yet
Development

No branches or pull requests

1 participant