We turned on User Provisioning this morning in Okta. We created a push group where the Active Directory (source) group has 7 members.
The group successfully provisioned to Atlassian Access, however only 6 of the 7 members were included in the group.
The account that wasn't included existed in the Directory in Atlassian prior to provisioning. It was enabled but had no product access defined.
I setup "no-email" invitations for the other 6 accounts prior to provisioning, and they all successfully provisioned, e.g. -their full names now appear instead of just their email address.
There are no error indications in the Audit log in Access, nor in Okta. In fact, Okta indicates 7 users were provisioned.
I tried enabling product access on the problem account and forcing a sync from Okta, but the group remains at 6 members.
Before I move on to Support I thought I would try here for suggestions or info.
In Okta, an account may not be properly synced into Atlassian if it has been assigned to the Atlassian Cloud app before provisioning was configured.
Have you tried to re-assign the user to the app in Okta? Check if there was a direct assignment for the user to the app in Okta and remove it. Remove and re-add the account to the pushed group.
We've recently released Jira User Sync/Provisioning plugin which provisioned all Users and groups from Cloud Identity provider(Okta) to Jira.
Here is the setup steps: https://plugins.miniorange.com/user-and-group-sync-user-provisioning-okta
Did you know Atlassian Access offers more than SAML single sign-on for Atlassian cloud products, like Jira and Confluence? Whether you're just starting to plan for your organization or in the pr...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events