Cannot link with en external application

I need to stablish a connection from JIRA with an external application via SSL.

The error received is : "The server 'https://greenhopper-dev.app.alcatel-lucent.com:443' is not reachable: javax.net.ssl.SSLException: java.security.cert.CertificateException: No name matching greenhopper-dev.app.alcatel-lucent.com found"

It seems like the server is not include in the certificates file /opt/atlassian/jira/jre/lib/security/cacerts, but the server is reachable via command line interface pointing to the same file .

> java -Djavax.net.ssl.trustStore="/opt/atlassian/jira/jre/lib/security/cacerts" SSLPoke greenhopper-dev.app.alcatel-lucent.com 443
Successfully connected

The option "-Djavax.net.ssl.trustStore="/opt/atlassian/jira/jre/lib/security/cacerts" " is include in the file setenv.sh and so ,is included in the variable JAVA_OPTS when jira starts.

please, any idea about why is failing the SSL connection?

Best regards

Jorge Sanchez

2 answers

0 votes

Is the cacerts file owned by and accessible to the user running the JIRA service? 

Yes. The cacerts file is accesible to the user running the JIRA service

That is odd, I cannot see a single thing that might even be wrong with this. 

I would check the running system as below and check the -D appears in there (it does not in mine, I've got a single key for a different reason)

ps -ef | grep -i jira
nic      10681 10666  0 18:41 pts/0    00:00:00 grep -i jira
charlie  14058     1  0 Jul02 ?        01:18:21 /opt/jira-7.1/jre//bin/java -Djava.util.logging.config.file=/opt/jira-7.1/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx1520m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -Djavax.net.debug=ssl -Djavax.net.debug=all -Djavax.net.ssl.keyStoreType=pkcs12 -Djavax.net.ssl.keyStore=/home/charlie/.certs/atlasclient.p12 -Djavax.net.ssl.keyStorePassword=***************** -XX:+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djava.endorsed.dirs=/opt/jira-7.1/endorsed -classpath /opt/jira-7.1/bin/bootstrap.jar:/opt/jira-7.1/bin/tomcat-juli.jar -Dcatalina.base=/opt/jira-7.1 -Dcatalina.home=/opt/jira-7.1 -Djava.io.tmpdir=/opt/jira-7.1/temp org.apache.catalina.startup.Bootstrap start

The cacerts file is owned and accesible to the JIRA service.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 05, 2018 in Jira Software

Jack Graves: Real Ale enthusiast with a knack for Jira Software implementation

@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...

96,834 views 4 14
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