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,457,987
Community Members
 
Community Events
176
Community Groups

I am unable to connect to Microsoft active directory with crowd 3.4

Edited

Hi Folks,

I am unable to connect Microsoft AD with crowd.

Crowd Version : 3.4

Settings are as follows :

Connector : Microsoft Active Directory

Hostname : ldap.gslb.internal.xxx.com

Port : 636

SSL : None

 

Result : test failed

There was a problem communicating with LDAP server. ldap.gslb.internal.xxx.com:636;socket closed;nested exception is javax.naming.ServiceUnavailableException:ldap.gslb.internal.xxx.com:636;socket closed

==========================================

Able to ping Microsoft directory server (ldap.gslb.internal.xxx.com) from crowd server.

Is issue with LDAP or in Crowd?

Regards,

Amar

 

1 answer

1 accepted

0 votes
Answer accepted
Marcin Kempa Atlassian Team Dec 15, 2019

Hi @Amar 

It seems to me that you are trying to connect over LDAPS (secure ldap protocol, port number indicates that), however you've entered hostname as:

ldap.gslb.internal.xxx.com

What happens if you enter there: 

ldaps://ldap.gslb.internal.xxx.com

or

ldap.gslb.internal.xxx.com

but with SSL set to: LDAPS?

 

If that also does not work can you verify that AD is configured to use LDAPS and this port is visible for Crowd?

Are you able to connect on 389 non secure port using standard ldap protocol (ldap://ldap.gslb.internal.xxx.com)

In order to check if LDAPS is up and running on AD (Windows Server) side you can do:

  1. In Windows click on Start and search ldp.exe
  2. In ldap window select Connection menu and fill following parameters:
    1.  Server - this is your host name (I assume this would be `ldap.gslb.internal.xxx.com`)
    2. port: 636
    3. Select 'ssl' checkbox
  3. Click ok. You should see information about established connection

 

Let me know if that helps,

Best Regards,

Marcin Kempa

Thanks Marcin Kempa

it worked for me :)

Added below line in Hostname and set SSL :)

ldaps.gslb.internal.xxx.com

Thank Again

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events