Groups provisioning using SAML SSO
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Permit to use in Gitlab groups already created and managed in Federation Identity (like Okta, Azure AD, etc...) rather than recreate and populate again in Gitlab. Goal is manage the group in only localization (centralize). So need to permit sync these groups (and members) in Gitlab.
Intended users
All users in Company with federation identity management want to provision on Gitlab the groups already exist in Azure, Okta, etc....
Further details
Like explain here (https://docs.gitlab.com/ee/user/group/saml_sso/scim_setup.html), tody we can provision the user using SAML. That could be good to permit provision the groups (with the members) already exist in company federation identity to Gitlab. After that, will permit to use these groups to manage permission on Subgroups or repository.
Proposal
Sync groups and users in gitlab. Create the groups in specifics folder in Gitlab et permit to use to give permission on Repository or subgroups.
What does success look like, and how can we measure that?
See the groups and the member like the source (and sync the updates). Permit to use these groups to manage permission.
What is the type of buyer?
Because link with the SSO to implement at Silver level.
Links / references
https://docs.gitlab.com/ee/user/group/saml_sso/scim_setup.html