This is pretty frustrating.
Have installed Jira Core 7.4.2 on Windows Server 2016
My intention is to create and Active Directory Sync that gets all users within an AD-group. But i get stuck on an error that my sync account cannot be found.
This is what i have filled in into the Configure LDAP User Directory page:
Directory Type: Microsoft Active Directory
Hostname: domaincontroller.domain.com (also tested netbiosname only)
Username: SVC-Jira-Sync@domain.com (also tested FQDN, ie CN=SVC-Jira-Sync,OU=etc etc)
Password: The password for SVC-Jira-Sync
Base DN: Tested both DC=Domain,DC=com and a more specific OU FQDN
LDAP Permission: Read Only
Left the rest default
When its time for testing the connection i fill in User name and Password for SVC-Jira-Sync (tested both UPN and FQDN) i get this:
Test basic connection : Succeeded
Test retrieve user : Failed
They might not be being selected by the rules you have set for what to synchronise or by permissions on the LDAP side.
I'm afraid without any errors on the Jira side, you'll need to debug what LDAP is doing. You could increase logging on the Jira side to see if you can get more detail from the connection it is trying to make (Admin -> logging and profiling, I think there's an LDAP or User directory class you can increase logging on), but this is starting to look like a problem with LDAP, not Jira.
One more thing after next try it were through sync error:
Caused by: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: LDAP response read timed out, timeout used:120000ms.; remaining name '/'
So it means we are having LDAP issue here, we need to check with LDAP part
When I am testing with all LDAP credentials the test connection is successfully done. But again when I click on synchronize it is full synchronize successful but in the logs, I can see none of the users are synchronized from LDAP to Jira. But on the Jira side, it is showing us as Test user failed but the user exists in the LDAP server. And also in the logs, I can see error related to that i.e.,
nested exception is javax.naming.CommunicationException: DOMAIN.COM:636 [Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching DOMAIN.COM found.]=
Kindly help me with this.
Thanks and Regards
Mone Dileep Kumar
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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