Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names matching IP address

[Prakash Krishnaswamy]

I am trying to tie Active Directory . Have installed certificate from windows admin as mentioned in following link 

https://confluence.atlassian.com/jira/configuring-an-ssl-connection-to-active-directory-229838539.html

But JIRA is throwing following error

Error:

Connection test failed. Response from the server:
AUSTAD-PRD.amat.com:636; nested exception is javax.naming.CommunicationException: AUSTAD-PRD.amat.com:636 [Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names matching IP address xxx.xxx.xxx.xx found]

[Pawel Rozek]

I know this is quite an old issue, but I had a similar error coming up. It seems that Atlassian documentation mentions that "Once the certificate has been imported as per the below instructions, you will need to restart the application to pick up the changes." That worked for me to resolve my issue.

[rrudnicki]

Hi Prakash, 

Can you verify if some IP Address or hostname has changed? Looks like your AD is not recognising the JIRA Certificate using  AUSTAD-PRD.amat.com with your xxxx.xxxx.xxxx.xxxx IP Address. 

Regards, 

Renato Rudnicki

[Sebastian Lotter]

Hi Prakash,

I saw the same exception after a java update to 7u7x as it is quite strict checking the IP in the certificate (see http://stackoverflow.com/questions/9185489/x509-subject-alternative-name-subjectaltname-ip-address-field). AFAIK there are two options:

a) Downgrade to 7u5x

b) Issue a new server certificate for your AD server including a subject alternate name for the IP of this server. No idea how this works in the windows world. For our Linux-Server it was a straightforward command line / configuration option.

Sebastian