Hello there,
We have been struggling for some time to use Atlassian Access integrated with Azure AD and have this working just fine to sync our customers across into JSM. The Line Manager attribute is present in Azure AD so is it just a case of adding this attribute into the sync? Do you have any documentation for this use case?
Hi Andy,
We had Atlassian Access setup via AzureAD before moving to Okta but it was pretty straight forward to configure with group based provisioning.
We had users added into dynamic groups based on attributes and groups provisioned onto Permission Schemes in each project via directory sync.
I would suggest raising a support case for this with the Atlassian Access team as they are very helpful.
We've tried to get the manager data synced via AzureAD with a few customers without success. I've added your feedback to our list of customers trying to do this setup. We'll let you know once we resolve the issue.
Sorry for the inconvenience.
Cheers,
Thanks for the replies - is it not something as simple as adding the Manager field into the Claim on the Azure side? I am not sure how we would then populate that on the Atlassian side?
@Andy Hockenhull the problem is on the field mapping needed so that Azure AD sends the manager field in the format we're expecting. We tried several variants like those below but none seem to work
We need to spend some time on our side to understand the payload sent by Azure to make sure customers can set the mapping properly.
@Eric, any updates on this?
Are there any updates on this? I'm running into the same thing.
It looks like you're new here. Sign in or register to get started.
