jira/bitbucket user migration to crowd

[Hitendra Chauhan]

We have goal to start using crowd for user authentication for jira, bitbucket and confluence. Crowd have delegated ldap directory that talks with company's ldap.

Current setup is :

1. Jira has delegated ldap authentication already configured and bibucket uses jira as user directory. This configuration is working fine and has around 300 active users which has jira-software-users access. There are many other user which do not have access at all but exists in jira as they are migrated from another defect tracking system.
2. Crowd have delegated ldap directory that talks with company's ldap. Nested ldap group are configured in ldap and used in confluence and works perfectly fine.

Now the objective is :-

Jira/Bitbucket and Confluence needs to be integrated with Crowd. Authentication and authorization should happened with delegated ldap directory created in Crowd.

I need the assistance to get the answer of atleast following questions to get started ?

1. What should be the high level steps and care should be taken to carry our this activity.
2. Since there are 300 active users in jira, it means we need 300 user license in crowd, but do we need to have more licenses as there are inactive user also in Jira /bitbucket which don't have the jira-software-users or stash-users rights.

[Laurens Coppens]

Hi,

1. As all of your users and groups are already in ldap and in crowd, you should be able to connect jira to crowd and then just put the priority of the crowd directory higher then the ldap directory, same for bitbucket.

2. You only pay for the active crowd users.

For example if you have 300 unique jira users and 200 unique bitbucket users, you need 500 user license.

If you have 300 jira users and 200 bitbucket users but 100 of those bitbucket users are also part of the 300 jira users, you only have 400 active users.

Hope this is clear.

Regards,

Laurens

[Hitendra Chauhan]

@Laurens Coppens thanks for the answer.

Licensing term is partly clear.

Just consider following scenaio.

Let say there are 10 users created in Jira. There are one or more entity associated with each of the 10 users and they were jira-software-users sometime.

But now 1 user's jira-software-users membership is removed, please note that the  associated entity like defect still exists.

Now how many crowd licensee will be needed ? 

[Laurens Coppens]

You only have to license the "Active" users in crowd, if you disable the user in crowd, it will still be linked to the old jira issues, but not longer active in jira and other apps, so no longer licensed.

You pay for all the users that have the ability to authenticate to one or more apps connected to crowd.

So you have to make sure to mark all the inactive users, inactive in crowd.

[Hitendra Chauhan]

@Laurens Coppens Thanks for clarification.