Migrating to SAML. Test environment, and user logout questions.

[Harry Sheppard]

Hi Everyone,

I am looking to migrate my organisation to use SAML single sign on, specifically with Azure AD, and have some a couple questions about the process.

One, is is possible to have some test environment, to ensure that SAML is working correctly, without affecting my users logins? Since Atlassian Access is configured organisation wide, I can't create a separate site to test in, can I?

Two, since user sessions will persist through the migration to SAML (as far as I have gathered from the documentation), will I need to have my users log out, then log back in before I would be able to manage their access through my identity provider (Azure AD)? If a user hasn't logged in with SAML, I would think that their session is not associated with their account on the ID provider. Or is the ability to disable users from the ID provider only available once I set up user provisioning?

Cheers,

Harry

[Daniel Ebers]

Hi @Amir Ghaemian

dealing with the same issue I found some Suggestions having a look (and a vote for!) could make sense:

• Allow Administrators to control managed users' associated sites and products
  https://jira.atlassian.com/browse/CLOUD-11072
• Prevent users under a verified domain for being able to sign up for a new Cloud instance
  https://jira.atlassian.com/browse/CLOUD-10325

Regards,
Daniel

[Amir Ghaemian]

I got it confirmed from a ATL TAM rep that it's not possible as Org admins to remove/cancel any Discovered products. They need to do that themselfs. The only solution would be to Deactivate the user(s) which should cancel the subscription

[Shane Johnson]

HAHA! I guess that is one way to force the end users to stop. 

[Shane Johnson]

I find it strange that we can't prohibit users from creating these in the first place. 

[Jan Odvárka]

same here,... one of our company member just made almost same site name and it looks like phishing site,... confusing user