Secondary Identity Provider - De-synced primary identity provider

Sam Dillon - ADM
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 18, 2024

Hi,

 

We were configuring an identity provider through Azure AD, with 200 users synced through the primary identity provider ADFS on the same domain. The second identity provider was configured and syncing only 7 users.

 

The secondary identity provider then was updated to use different groups to sync users with, these were newly created groups in Azure. As soon as this was done all synced users were deactivated, even the administrators and now no one is able to sign into Atlassian, nor the admins to reconfigure this to fix.

 

I am unable to raise a support as I need to sign into my account, which I am unable to do.

1 answer

0 votes
Sam Dillon - ADM
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 18, 2024

After searching, it appears to require the same resolution as the below. I really just need someone from Atlassian to see this and reactivate my account so I can reconfigure the identity provider for the organisation.

 

https://community.atlassian.com/t5/Jira-Service-Management/My-Account-is-deactivated-suddenly/qaq-p/2299656#M131238

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events