nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Delegated Crowd directory without LDAP Group

Ansar Rezaei

1- I'm new to crowd. We have lots of group in LDAP directory that uses for OS security group and I don't want to use them in Atlassian applications. I create a LDAP connector that bring every users and groups from Microsoft LDAP and I create a Delegated Directory in order to import users from LDAP to I need to have a Delegated LDAP Directory in crowd without that groups. Is it possible to change the configuration of Crowd Directory to achieve this?
2- If I have new users in LDAP directory, How I can sync them with Delegated directory?

Thanks For your answers.

image2017-1-18 10:49:0.png

image2017-1-18 10:50:10.png

crowd.JPG

Accepted answers

Bruno Vincent

Hi Ansar,

If your main concern is not to import the AD groups in Crowd, you actually have two options.

1st option: Create a (single) LDAP connector directory and edit the group object filter in the configuration tab so as to fetch only Atlassian applications groups

2nd option: Create a (single) Delegated authentication directory and then manage your Atlassian applications groups locally in this Crowd directory. You do not need manual synchronisation for new AD users. As detailed in the documentation:

If a user logs in successfully via LDAP authentication but does not yet exist in Crowd, Crowd will automatically add them to the Delegated Authentication directory

All comments

Bruno Vincent

Hi Ansar,

If your main concern is not to import the AD groups in Crowd, you actually have two options.

1st option: Create a (single) LDAP connector directory and edit the group object filter in the configuration tab so as to fetch only Atlassian applications groups

If a user logs in successfully via LDAP authentication but does not yet exist in Crowd, Crowd will automatically add them to the Delegated Authentication directory

Ansar Rezaei

Hi Bruno
Thanks for your comment.

I don't familiar with crowd and Active Directories and I do this job according to my role in organization as JIRA Administrator. Which value should I provide in group object filter in order?

For your 2nd option I follow that instruction but It brings all of groups in Active Directory.
Please provide more detailed answers, as I say I'm new to crowd.

Thank you very much

Bruno Vincent

Hi Ansar,

1st option: you have to enter an LDAP filter as detailed on this page: https://confluence.atlassian.com/display/CROWD/Restricting+LDAP+Scope+for+User+and+Group+Search

For instance, if you enter the following value, you will only get the AD groups whose name starts with jira:

(&(objectCategory=Group)(cn=jira*))

2nd option: That's because you created an LDAP connector directory in addition to the Delegated Authentication directory. You just need one single directory (the Delegated Authentication one). If you do not want anything related to AD groups in this directory, please also disable Synchronise group memberships in the connector tab.

Ansar Rezaei

Hi Bruno
Thanks for your help

I try first option and it work for me.

But I didn't understand 2nd Option, I have a Microsoft Active Directory in our organization, If I define a delegated connector, how I can import Active Directory users without defining and LDAP Connector in Crowd?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

crowd

crowd-administration