The cause is Jira that connects to itself, and if you have a proxy installed, the SSL certificate must be well configured in the Java environment
The Atlassian solution is:
And our proposed solution is:
- Export the SSL certificate and import it in the Jira JRE security CA cert file (and in the system Java security CA cert file)
- The proxy MUST be configured to redirect to the url (not to localhost)
- openssl s_client -connect jira.example.com:443 < /dev/null | sed -ne ‘/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p’ > public.crt
- keytool -import -alias jira.example.com -keystore /etc/pki/java/cacerts -file public.crt
- keytool -import -alias jira.example.com -keystore /opt/atlassian/jira/jre/lib/security/cacerts -file public.crt
Thanks to Riccardo for this solution!
Post by MrAddon
To find keytool is inside the JRE
To find the cacerts use:
Default password: changeit
LikeLike
Hi,
Do we need to install the SSL cert which lives on the ELB in AWS?
Or the public SSL cert we see in the browser?
Thanks
Richard
LikeLiked by 1 person
hello Richard is the public SSL cert of the browser. Best regards!
LikeLike