Application groups in crowd or application
Asked by sri deepthi:

We are planning to setup a complete ALM solution with JIRA+confluence+fisheye (crucible)+Bamboo and would like to have authenticated with LDAP via Crowd.

Can you please advice me on having groups for applications created at crowd or application end. we already have 70 groups in jira and want to import them to crowd.

If we create users/groups at crowd is there a mechanism to sync the groups and users back to application, where even if we loose the connection with crowd, would like to have another user directory setup directly talkin got LDAP.

please advise me on this.


Answers:
author: Septa Cahyadiputra
body: > When we have crowd to authenticate users logging into jira for the first time will have an account created in crowd and validated with LDAP ( Deligated).

I don't think this is possible as Crowd Delegation Directory does not work that way. You will need to add the user by manually instead of automatically create when the user log-in to JIRA.

As mentioned previously you could import the user from JIRA though.

Cheers,

Septa Cahyadiputra

comments: author: sri deepthi
body: I have users created in crowd when they try to login fisheye, which is currently hookedup with crowd.

Being we already have users (1200+) and 75+ groups in jira we planned to import them into crowd where there jira usernames are same as in LDAP. The new users will automatically get created in crowd and we manually add them to the requred jira groups


author: Septa Cahyadiputra
body: > When we have crowd to authenticate users logging into jira for the first time will have an account created in crowd and validated with LDAP ( Deligated).

I don't think this is possible as [Crowd Delegation Directory](http://confluence.atlassian.com/display/CROWD023/Configuring+a+Delegated+Authentication+Directory) does not work that way. You will need to add the user by manually instead of automatically create when the user log-in to JIRA.

As mentioned previously you could import the user from JIRA though.

Cheers,  
Septa Cahyadiputra


author: Septa Cahyadiputra
body: > When we have crowd to authenticate users logging into jira for the first time will have an account created in crowd and validated with LDAP ( Deligated).

I don't think this is possible as [Crowd Delegation Directory](http://confluence.atlassian.com/display/CROWD023/Configuring+a+Delegated+Authentication+Directory) does not work that way. You will need to add the user by manually instead of automatically create when the user log-in to JIRA.

As mentioned previously you could import the user from JIRA though.

Cheers,  
Septa Cahyadiputra


author: Septa Cahyadiputra
body: Hi there,

To import your users and groups from JIRA you could use [Crowd user importer feature](http://confluence.atlassian.com/display/CROWD/Importing+Users+from+Atlassian+JIRA).
> If we create users/groups at crowd is there a mechanism to sync the groups and users back to application

When you integrate Crowd with JIRA 4.3 and above, JIRA will have the ability to [synchronize](http://confluence.atlassian.com/display/JIRA/Connecting+to+Crowd+or+Another+JIRA+Server+for+User+Management) the whole users and groups [configured](http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+JIRA) for its. If you allow [JIRA to write into Crowd](http://confluence.atlassian.com/display/JIRA/Connecting+to+Crowd+or+Another+JIRA+Server+for+User+Management#ConnectingtoCrowdorAnotherJIRAServerforUserManagement-CrowdPermissions) it will be able to add users and groups directly into Crowd also.
> where even if we loose the connection with crowd, would like to have another user directory setup directly talkin got LDAP.

In order to do this, than you will need to configure [JIRA to integrate with LDAP server](http://confluence.atlassian.com/display/JIRA/Connecting+to+an+LDAP+Directory) and place it at a lower order than Crowd directory at your "User Directories" menu.

This configuration will allow JIRA to search Crowd first, then if its unable to authenticate against Crowd, JIRA will try to authenticate it against LDAP server.

Hope it helps.

Cheers,  
Septa Cahyadiputra

comments: author: sri deepthi
body: Thanks Septa for quick reply, and making me understand.

We don't want to allow jira to create users in crowd as we have connected crowd with LDAP and we do want to implement SSO.

When we have crowd to authenticate users logging into jira for the first time will have an account created in crowd and validated with LDAP ( Deligated). If i have LDAP as a second directory, I believe this will not happen and we might not be able to implement sso for the account as Jira finds the user in direct LDAP directory.

Sorry for the long explanation. Please clarify this and put me in the right path.

Regards,

Sri