SSO enforced on git activity: only top-level group owners should be able to bypass this with Private Access Token
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
When SSO is enforced on git activity, only owners of the top-level group should be allowed to bypass SSO by using Private Access Tokens.
User experience goal / Proposal
At this point, a direct owner of a subgroup is also able to bypass SSO by using a Private Access token. However, owners through inheritance are not able to do this. In order to correct this behavior, we would like to change this so that only owners of the top-level group will be allowed to bypass this.
Further details
This change would make the behavior clearer for the customer as the behavior will not change depending on being a direct owner / owner through inheritance.
Available Tier
Premium / Ultimate
What does success look like, and how can we measure that?
Only top-level group owners will be able to bypass SSO with a Private Access Token when SSO is enforced on git activity.