SAML SSO using Atlassian Access

[Ahsan Muhammad]

Hi,

We are looking to subscribe to Atlassian access for our site which is "companyName.atlassian.net". The reason for subscription to Atlassian access is that we want to enable SSO for Confluence, JIRA and Bitbucket via our own custom IDP for user authentication and authorisation. Right now all the users login through Google sign on. Can we also keep the Google sign on while testing the option of SSO via our IDP, and, it will not affect the users from accessing the content on Atlassian? If there is not the possibility of enabling two different sign on, i.e. Google and our custom IDP then we are thinking of creating test site for testing SSO and then replicating everything on our live Atlassian site. 

Best Regards,

Ahsan

[Matthias Fleschütz · Accepted solution]

Having some results after working with the Atlassian support:

simply not possible at the moment, as Atlassian Access would require

* the atlassian account id of the manager or

* the email address of the manager

Unfortunately the attribute can only be filled by Azure AD with the account GUID on Microsofts side.

[Eduardo Oliveira]

Hi @Matthias Fleschütz and @Arnd Layer  - Not sure if you already solved this issue, but if you're open to using an app, I would like to share another potential solution for Jira that may help in this scenario - MindPro Sync.

This app allows you to integrate OKTA, Azure AD, or OneLogin with Jira and JSM and retrieve user attributes (phone, location, department, etc..), map them in Jira custom fields and display this data directly Jira issues or JSM requests (and portal)

All the best,
Eduardo - from MindPro, a Marketplace Partner.

[Matthias Fleschütz]

Hi @Eduardo Oliveira - Mindpro Apps 

thanks, please don't get me wrong: that's really some basic functionality that Atlassian should provide if I already pay ~900 bucks / months for Atlassian Access!

[Arnd Layer]

Having the same problem. Adding to this, the linked documentation is currently not available. Does this have something to do with the renaming to Atlas?

[Matthias Fleschütz]

Additional info: there is now an accepted bug as well because of different HTTP method endpoints supported / or not for manager attribute: [ID-7978] Automatic Provisioning: PATCH API endpoint to update user attributes doesn't work with manager field - Create and track feature requests for Atlassian products.