You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you are interested into the same feature.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: 29.0.6
Is your feature request related to a problem? Please describe.
In Keycloak it is possible to have nested (hierarchical) groups like "/parent/child". So if a user is member of child group it is implicitly also member of parent group.
Nextcloud doesn't support nested groups.
Unfortunately at the time being keycloak can only send the whole group path "/parent/child" or only the group the user is explicitly member of, so "child'.
In a lot of use cases, having an option which supports flattening the groups would be enough. Like
"/parent/child" becomes the two groups:
parent
child
Would be nice if that would be an selectable option for the user_oidc app.
The text was updated successfully, but these errors were encountered:
How to use GitHub
Feature request
Which Nextcloud Version are you currently using: 29.0.6
Is your feature request related to a problem? Please describe.
In Keycloak it is possible to have nested (hierarchical) groups like "/parent/child". So if a user is member of child group it is implicitly also member of parent group.
Nextcloud doesn't support nested groups.
Unfortunately at the time being keycloak can only send the whole group path "/parent/child" or only the group the user is explicitly member of, so "child'.
In a lot of use cases, having an option which supports flattening the groups would be enough. Like
"/parent/child" becomes the two groups:
Would be nice if that would be an selectable option for the user_oidc app.
The text was updated successfully, but these errors were encountered: