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
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