We have a Bamboo Instance which uses the internal User Management System. We now want to migrate this to use Crowd but we are not sure what will happen to the existing user accounts which exist in the local bamaboo user directory.
We followed the convention of creating users in Bamboo using their windows AD usernames. These are also what Crowd uses in out crowd configuration. The end result is we'll have duplicate usernames in both crowd directories and in Bamboo's Internal user directory.
What is the best way to switch across to using Crowd without getting into the situation where duplicate usernames are causing access issues to Bamboo
I believe you will not have problem with this configuration since the users in crowd and internal uses the same username. Basically when you use the crowd directory for user management, the internal users are automatically ignored by the Bamboo server. In effect, crowd directory can not be used in conjunction with any other directory. Having said that, the internal users are not deleted from the database but kept in the table "users" which is inactivated when crowd is the user management medium.
One problem you might face is when the users in internal directory have different group membership compared to the crowd. In which casee, you will have to do some manual mapping between users and the groups.
Hope that helps :
...roperties: -Dbamboo.bitbucket.cloud.use.workspace.api=true There are patches available for Bamboo versions 6.8.3, 6.9.2, and 6.10.5 on the bug report that add support for the System Property. T...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events