Atlassian Acces + Azure SSO / Conditional Access with named locations

[Jonny Klaas]

Hey there, 

we recently setup Atlassian Access with our Azure AD to secure our logins. 

In the next step we want to use "conditional access" to enforce the use of VPN and specific public IPs. I've setup a rule and the login will be blocked if I connect from a foreign IP address.All fine. But if I disconnect the VPN from a valid session the login at Jira still persists? All other Apps like Google Gsuite noticed very fast, that the conditional requirements are now missing. 

So is this behavior intended or just a bug? when will the user be kicked out from the session? The general logout time would be way too long

Regards,

Jonny

[Stephen Sifers · Accepted solution]

Hello Luis and welcome to the Community!

Thanks for the detailed description of your issue and the problem with having the +1 email that's preventing your access. I would be interested to know if you're able to go the following and attempt a login with your +1 account:

• Navigate to: https://id.atlassian.com/login/select-account
• Attempt to log in with your +1 account
  • Are you routed back to your main account?

While not desirable, the easiest path forward may just be changing your SSH key (Less time to make the change). You can do so by following Set up an SSH key.

Regards,
Stephen Sifers

[Luis Gonzalez]

Excelent, @Stephen Sifers Your solution worked!

I was able to see the attlasian account there (https://id.atlassian.com/login/select-account).

The Steps I did to recovery the SSH Key were:

1-) I clicked on the +1 account, then I entered to the +1 Atlassian account.
2-) Clear the bitbucket.org Cookies (This was necessary because the current cookies corresponds to the main account logged):

 
3-) Click on the Menu + Bitbucket:

4-) Then I was able to enter to the +1 Bitbucket account and remove the SSH Key to be able to reuse in the main account.

With those steps I didn't need to create a new SSH Key.

Thanks so much!