What are the impacts to the existing users created in the Bamboo internal user directory when you repoint Bamboo to use Crowd

[Shane Parkinson]

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

[Sultan Maiyaki · Accepted solution]

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 :

Regards,

Sultan