the following situation exists:
The user management of Confluence is linked to an AD via LDAP. The AD is the leading system.
A user has too often entered his wrong password in Confluence so that his Confluence account is blocked and his AD account is set inactive.
Even if the AD Admin activates the account, the user still has to be reactivated by the Confluence Admin in Confluence, too.
Is there a possibility that only the activation in the AD is necessary? So that this activation is synchronized to Confluence. Without activation code in Confluence.
Since Confluence 5.3 the disabled flag from AD has been synchronized over to Confluence.Provide Confluence support for Active Directory's "Account Disabled" flag If a user locks out their AD account via too many bad passwords, and the AD admin unlocks the account, the user will be reactivated in Confluence during the next synchronization. The default synchronization interval is one hour so that delay may be what you are experiencing when you find you have to manually enable the user in Confluence. You can either wait an hour, activate the user as you have been doing or else manually sync the AD User Directory at Confluence Admin>User Directories. Please see Synchronizing Data from External Directories for more details.
If you sync the directory and the user is still disabled, please let me know so I can investigate further.
More and more people are building their careers with Atlassian, and we want you to be at the front of this wave! Important Dates Start the Certification Prep Course by 2 April 2019 Take your e...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs