Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

LDAP usage in Crowd 3.1.3

Deleted user Apr 11, 2018

Hi,

we want to use Crowd for the user management of several Jira and confluence servers with different users and groups. We also want to use our company wide Active Directory (where we don't have writing rights) as user base and authentication server. How do we get on for that?

I have installed the trial version of Crowd on a server and configured our Active Directory as Crowd Delegated Authentication directory. The test was successful, but even an empty user search does not give any result.

I followed the instructions on https://confluence.atlassian.com/crowd/getting-started-with-crowd-197298051.html

Now I am in doubt whether I should have chosen the first LDAP variant instead of the "delegated authentication"? I thought this couldn't be it as we can't store our Jira and confluence groups in the company Active Directory.

 

1 answer

1 accepted

0 votes
Answer accepted

Hi @[deleted]

That's right, you should have chosen an LDAP directory connector instead of a delegated authentication one: https://confluence.atlassian.com/crowd/configuring-an-ldap-directory-connector-18579550.html

With delegated authentication, users are only retrieved in Crowd after they successfully authenticate.

You don't need to have any write privilege on AD for standard LDAP directory connector. The connector will synchronize users and groups from AD into Crowd and won't do any write operations on AD, at least if you don't want to. You should configure the connector with an AD user that does not have any write privileges on AD.

Deleted user Apr 11, 2018

Merci beaucoup!

You're welcome @[deleted]!

I've edited and completed my answer as some community readers might want to use Crowd to do write operations on AD, which is also feasible. If you do not want Crowd to write anything on AD:

  • Configure the connector with an AD read-only user
  • Make sure to uncheck all Add/Modify/Remove boxes in the permissions tab of your directory in Crowd's console

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Happy New Year and Welcome New Marketplace Partner Program Partners!

Happy New Year! We hope you all had a safe and restful holiday season. 2020 was a unique year full of unforeseen events; however, as we enter the new year of 2021, we’re optimistic for the light at t...

474 views 6 18
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you