2 Directories in Crowd connected to 2 branches of LDAP - can user-group mgmt be done in JIRA


We are planning the deployment architecture for Atlassian suite for our enterprise.

We will have both employees and non-employee users using the Atlassian Suite.

One possible configuration that we are favoring is that we will use OpenLDAP to maintain users and groups. We will create 2 different OUs or branches in LDAP and possibly have replication at LDAP to other geographies.

Our concierge uses JIRA for creating users and groups, right now. We are wondering if we can continue to use JIRA in the below scenario to be the user interface for managing users and groups.


connected user |

JIRA -----------> Crowd ---------> Dir1-------> Branch for employees

| | |

| | | | (mapping)

| |group | /

| -------| Branch for groups

| -------|

| | group| | (mapping)

| | | /

|-----------> Dir2-------> Branch for non-employees


Now, if we give JIRA application privileges to Crowd for creating users and therefore to LDAP, does that mean that if we create/manage users and groups and memberships they will be created properly in LDAP?

If not, what is the best user interface you can propose for easily creating users and groups and memberships in atlassian suite to the OpenLDAP Directory.

We are using JIRA, Confluence, Fisheye and doing SSO with Crowd. We are open to deploying any plugins (like Teem) that will help in managing users and groups and memberships for the whole suite.

2 answers

1 accepted

0 votes
Accepted answer

Hi, I got an answer from Atlassian support on support.atlassian.com. Apparently, if we use JIRA to create the users and groups in the above scenario, where we have 2 different branches of LDAP, JIRA would create the users and groups in the first directory mapped to it only. If we want users and groups in separate branches of LDAP, we could use 2 JIRA servers instead of 1, one mapped to each directory of crowd and further to different branches of LDAP.

Hi there,

If the Crowd directories configured to have the permission to write into your OpenLDAP and the LDAP user that used by Crowd to bind your LDAP server has the privilege to write into your LDAP server, your setup should work fine.

Hope it helps.

Septa Cahyadiputra

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Agile

How Scrum works? It starts with training and education

To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?”  That question applies to both implementation and improvements on the Scrum framew...

119 views 3 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you