LDAP SSL errror with correct subject alternative DNS in cert

This question is in reference to Atlassian Documentation: java.security.cert.CertificateException: No subject alternative DNS name matching found

When i look at my LDAP-Server cert with the openssl client i get a correct  X509v3 Subject Alternative Name.

But JIRA still fails with "javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names matching IP address"

any ideas?

2 answers

1 accepted

0 votes
Accepted answer

I found this issue:

https://jira.atlassian.com/browse/BSERV-7741

So it seems to be more a problem with the buildin JRE that comes with Jira, which is still 1.8.0_51  

Would be nice, if Atlassian could pack JIRA with a current JRE

Ok, my fault.

My testing-machine is v7.1.1 with JRE 1.8.0_51
My production-machine is on v7.1.4 with 1.8.0_74-b02

I need to check if it will run on later 

JRE 1.8.0_74-b02  (in JIRA v7.1.4) solves the LDAPS SSL error

Make sure that both the short and FQDN is presented in the certificate alt names. Commonly certs are issued with FQDN but site's visited via the short name, and this can cause these kind of issues.

 

 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,952 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you