Supporting multiple iDPs. ... Is this NOW a feature?

[Matt Olson (old, dont reference)]

Our company needs to make a critical decision to move to the Atlassian Cloud, or another option.

A requirement is to be able to set up multiple iDPs.

We have an on-prem Confluence instance that we would need to connect to a JIRA cloud, and the connection is split between four brands.

We used a SAML SSO plugin for this in the past, but I'm not seeing that this plugin is an option for JIRA cloud.

In the past, Atlassian said it was part of the roadmap. 

1) Is this now a feature with Atlassian Access?
2) Is this a feature with Atlassian Access as a standalone product? (we may be migrating to Atlassian Cloud Premium, not Enterprise)
3) Is this possible connecting an on-prem Confluence with SAML SSO plugin, to a JIRA Cloud instance using Atlassian Access?

What is the latest?

[Boris MBOUMEHANG · Accepted solution]

Hello Sadaf, 

I checked the TXT records of both ibexglobal.com and ibex.co domains, and they are completely different:

ibexglobal.com -> atlassian-domain-verification=5TJO6dykk0hSmmgXmm13A55gMuBiNmXYm6b7VT3L8Kq7GE8RkL3uCUFay/94ViVq
ibex.co -> atlassian-domain-verification=P7xOlhjlYJl5A-jCaKys4OLfHXybr7veCFrZCI4ZtUhu4bxWYMdbt4ToqHG0/UQh

That probably means that there are verified in two different Atlassian organizations. So, on my opinion, only the organization admin where the domain ibex.co is verified can modify the email addresses. 

Can you confirm that that is what you are trying? If so, how does the organizational admin try to change the email address of the users with ibex.co? Does he try directly in the Managed accounts menu (through https://admin.atlassian.com)? 

Best regards

Boris

[Boris MBOUMEHANG]

Hello Sadaf, 

I checked the TXT records of the two domains you mentioned, and I noticed they where different: 

ibexglobal.com -> atlassian-domain-verification=5TJO6dykk0hSmmgXmm13A55gMuBiNmXYm6b7VT3L8Kq7GE8RkL3uCUFay/94ViVq

ibex.co -> atlassian-domain-verification=P7xOlhjlYJl5A-jCaKys4OLfHXybr7veCFrZCI4ZtUhu4bxWYMdbt4ToqHG0/UQh

That probably means that the two domains where verified on two diffrerent Atlassian organizations. So, I think you have to check if it is the organization administrator of the correct organization (the one with ibex.co) who tries to edit the email address of ibex.co users. 

If so, how does he try to edit that email address? Does he try directly through the Managed accounts section of admin.atlassian.net?

Regards,

Boris