dependency-track

dependency-track copied to clipboard

The enhancement may already be reported! Please search for the enhancement before creating one.

Current Behavior:

You have to use object-ID's to specify which groups you want, for example from an Azure AD, to authenticate and authorize. When viewing the OIDC Groups tab, only the Object-ID's are visible which makes it very hard to distinguish groups from each other.

Proposed Behavior:

When adding a Group you must specify the name (Which is the name of the group in your AD or user management application) and an ID (which is the object-ID from that specified group)

This will make OIDC Group management more uncluttered and easier to use in larger scale organizations

This is yet another area where different SSO providers have different behaviors. In Keycloak for example, there is no such thing as Group ID. So we can't make that additional field mandatory.

But I agree that in case of Azure AD only seeing the cryptic Group ID is not very user friendly. Maybe an optional Display Name would suffice?