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,293,785
Community Members
 
Community Events
165
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
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

220 views 0 6
Join discussion

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