[2024.06.0] Cannot create groups with the same name about authentik HOT 4 CLOSED

This is intended, we'll need to add this as a "breaking" change to the release notes @rissson @tanberry

from authentik.

Thanks for clarifying @BeryJu .
I still think that having groups with the same name could be useful in some scenarios, for example using nested groups.
Is there any technical or design reason which cause the removal of this feature?
Without this feature, nesting groups may be less useful, and users will end up using a flat group setup..

This feature is also beneficial for mapping groups to Apps. For instance, OIDC apps obtain group names via claims. If group names are unique, OIDC applications may end up with unnatural group names, such as /org/division/administrators instead of simply administrators. While this issue can be resolved through policies, it requires additional effort.

from authentik.

@marcportabellaclotet-mt the main reason fir this is compatibility with external systems (it was changed as part of adding GWS support), as with a lot of external systems that are also identity providers (like google workspace and entra), group names are unique. Also with how groups are currently returned in scopes and in the API it can be quite difficult to differentiate two different groups with the same name (when not using the UUID). This might be something we'll revisit in the future or make configurable in the future

from authentik.

That makes a lot of sense.
Making this configurable could be useful for different scenarios.
Thanks for the explanation @BeryJu .

from authentik.