I am trying to tie Active Directory . Have installed certificate from windows admin as mentioned in following link
But JIRA is throwing following 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]
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.
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.
Welcome to your weekly Jira Ops Early Access program update, where we’re sharing news and updates on Jira Ops progress as we work toward our 1.0 release. If you ever want to drop us feedback or ideas...
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!
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