You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, We are planning to migrate all our Atlassian tools to new servers. They all use Crowd for their user management. All the apps except Bamboo allow the use of local users concurrently with the Crowd ones.
Where we are migrating to cannot see the existing crowd server. So how can I migrate Bamboo? I have performed a trial migration, and after importing the data to the new empty instance am unable to login as user management fails due to not being able to see the old Crowd instance.
Hi Jeyanthan, thanks for the reply. I understand that given that the legacy Crowd is no longer visible I have to swap to the local user admin. However, if we ever had any users configured in the local user repository I am unaware of them. So after swapping, how can I log in as an administrator?
When you first set up Bamboo an admin user is created. You can use this user to log into Bamboo - if you forgot the password, you can reset it using the procedure described in https://confluence.atlassian.com/bamboo/restoring-passwords-to-recover-admin-users-289277354.html
Premier Support Engineer
You can follow the steps in this document to revert Bamboo to local user authentication and then reconfigure Crowd authentication:
Premier Support Engineer
If you are using Crowd as your User management, what you are trying to achieve is not currently possible in Bamboo. You can only use Crowd as a user repository at a time and not with local user repository. As you notice, under Overview -> User repositories you could only choose one among the three distinct options for user management:
When your Crowd server is unreachable, you would have to manually revert Bamboo's User Management to Internal Directory like mentioned in the above link and then configure Crowd back.
However, if you are using LDAP, you have the option to use both LDAP and Bamboo internal directory working together as you will be choosing "Custom user repository" like mentioned here.
Hope that clarifies.