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?
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:
What happens if you enter there:
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:
Let me know if that helps,
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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