You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
According to the documentation in user provisioning, you can manage groups and provisioning by groups after connecting to an identity provider. However, what happens to existing groups and group membership when converting to an identity provider?
It depends on how you set it up. You do not have to have all groups connected to your identity provider. Actually, I would just only one or two, depending on the need. When you connect the group to the provider, though, it will lock it in Jira and can only be updated by the provider.
Hey John, thanks for responding. I have spent time testing this and I agree with you it is easier to manage syncing just a few groups through the identity provider. I have also confirmed that existing groups and membership is not affected as long as those groups are synced across.
Hey Jill - the default groups are the groups that will automatically be given to the user when their account is setup. If you have a separate group connected to your ID provider (AD, Okta, etc.) then by definition the user will be placed in this group. So you don't need to set it as a default group.
But I would also grant access to the product to this ID provider established group just to avoid any connection issues for the user.