Atlassian group push to link existing groups no longer displays groups that were created in Atlassian and not pushed from Okta.
The following error may also be encountered:
Errors reported by remote server: Resource [GROUP]: with displayName already exists.
- Atlassian
- Group Push
- Okta Classic Engine
Group conflicts occur when groups have the same name in Okta as groups that already exist in the Atlassian organization.
Atlassian cannot sync groups from Okta when the group is a default access group on the Atlassian product site. To sync the group, change its default access status and then sync it.
Refer to Atlassian Cloud documentation for more information on supported group operations, which explains that any group that is marked as a default group cannot be managed via SCIM integration.
- Review groups before performing a sync
Before syncing and replacing the groups, we’ll share a list of group names and a breakdown of the membership changes that will happen. Here is a screenshot with a sample breakdown.
- Name of the group.
- Product access for the group.
- Name of each site for the group.
- Number of users added or removed if decided to overwrite the group.
- Sync groups after review
There is flexibility to sync one group at a time or to sync all groups at once.
To review and sync groups:
-
Go to the organization at admin.atlassian.com.
-
Navigate to the Identity provider directory.
- A warning message appears with the number of groups we could not sync.
- Select Review groups.
- Review member changes (members to be added or removed from the group).
- Select Sync group.
- Group sync is complete
