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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,557,284
Community Members
 
Community Events
184
Community Groups

Crowd Connector to AD

Hi

i'm trying to connect my Crowd server to the company AD, i'm always getting 'authorization fail'.

Does the user I've entered in the connector must be an Admin on the AD container (OU)? (or READ permissions are enough?)

Also, the AD guys told me that the connection to the AD must be with Kerberos Ntlm protocol, Does Crowd supports that? (or there is no way i'm connecting it to our organization AD)

 

Thanks.

3 answers

1 vote
Bruno Vincent
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 10, 2016

The user that you set while configuring the connector does not have to be an admin. Any standard user with read rights is enough.

The AD connector in Crowd uses standard username/password authentication for LDAP (or LDAPS). Though it is not supported by Crowd, LDAP requests to Active Directory can also be authenticated with Kerberos but I would be very surprised that your organisation forbids standard username/password LDAP (or LDAPS) authentication.  

Hi

Thanks for the quick answer, can you please explain what i need to do to authenticated with Kerberos while defining my connector?

(do i need to change my url from "ldap://...." to something else?)

 

Thanks!

Bruno Vincent
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 11, 2016

Hi @lilach feit,

You can't do that as it is not supported by Crowd. As of today the LDAP connector in Crowd only allows you "bind" to AD with a username/password, not with a Kerberos ticket.

Hi Steve, 

It needs to be KERBEROS protocol 
NTLN is blocked in our network. 

Does Crowd supports KERBEROS protocol ? 
If so, please let me know what is the configuration required ?


Thanks. 

0 votes
Steve Behnke [DiscoverEquip.com]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 10, 2016

Can you explain the requirement again? The connection between crowd needs to be Kerberos/NTLM?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events