Okta Group Push Error in Atlassia

[Bikram Thapa]

The group push feature was working fine before. However, during the renewal of license with Atlasssian, the Atlassian Access was turned off ( accidentally by Atlassian) disabling SSO and API Integration with Okta. Once the feature was turned on, the SSO piece worked as normal without having to reconfigure. However, the API Credentials failed, not allowing user provisioning and needed to be updated. After the credentials were updated, there are bunch of Groups throwing error without any description on the Okta side. When a new user is added to the group, the user can SSO in Atlassian Jira but is not part of the groups, or does not see the project board as there is a Group Error preventing correct sync. Any idea on how to resolve this issue ?

[Narmada Jayasankar]

Hi Thapa,

I assume you are using SCIM user provisioning to push the groups from OKTA to Atlassian. If so, you will need to reconfigure SCIM when Atlassian Access is turned off and turned back on.

If this doesn't help, please file a support ticket so that our support team can help.

Thanks,

Narmada Jayasankar

Lead Product Manager, Atlassian Access

[Bikram Thapa]

How do you reconfigure a SCIM when there are two SCIM directories. Prior to the disruption, we had a SCIM directory. Then, looks like a new SCIM directory was created, with fresh sets of API credentials for Okta after the Atlassian access got turned back on. There is no sign of old directory under Directory. However, There are two groups: All members for directory - <directory_id> each tied to separate Directory ID. there a way to merge those two SCIM directories ? Also, do you mean regenerate a new API credentials for the old directory when you say "reconfigure SCIM"? How is that possible when there is only 1 Directory  listed under Directory tab. 

[Sanford Banks]

Was this issue ever resolved? If so, what was the resolution? We are experiencing the same issue now.