Issue Summary

The process described inside the Lockout recovery process page does not work when SSO is enabled.

Steps to Reproduce

1. Enable SSO in Bamboo.
2. Follow the steps inside the Lockout recovery process page to access Bamboo with the "recovery_admin" account.

Expected Results

I am able to log in with the "recovery_admin" account.

Actual Results

I'm not able to log in with the "recovery_admin" account. Bamboo says that the credentials might be wrong or the user does not exist.

Workaround

1. Stop Bamboo.
2. Revert back to using the default Bamboo authenticator.
   • Comment out the following line inside the <Bamboo server home directory>/atlassian-bamboo/WEB-INF/classes/seraph-config.xml file:
     seraph-config.xml

     <!-- <authenticator class="com.atlassian.crowd.integration.seraph.v25.BambooAuthenticator"/> -->
     

   • Add the following line after the one mentioned above:
     seraph-config.xml

     <authenticator class="com.atlassian.bamboo.user.authentication.BambooAuthenticator"/>
     

3. Follow the steps inside the Lockout recovery process page.
4. Start Bamboo.

At this point you should be able to access Bamboo again using the "recovery_admin" account. Once you've sorted out the problem connecting to Crowd you will need to revert changes made in step 3 in case you wish to enable SSO again.