Get 500 error after adding Djavax.net.ssl.keystore

[Jacob Gude]

Hello,

I'm trying to add Google Secure LDAP to our Jira instance. I converted the provided Google certificate and Key to a .jks file. When I add the following to the setenv.sh file, stop, and then restart Jira, Jira starts up but ends up with 500 error message. I've scoured through the logs and cannot find anything that is causing this issue. 

1. Edit /opt/atlassian/jira/bin/setenv.sh.
2. Find the JVM_SUPPORT_RECOMMENDED_ARGS setting.
3. Add “-Djavax.net.ssl.keyStore=/opt/atlassian/jira/jira-ldap.jks -Djavax.net.ssl.keyStorePassword=password”, replacing “password” with the password you selected above.

Using Googles instructions from 

https://support.google.com/a/answer/9089736#

[Edwin Kyalangalilwa · Accepted solution]

Hi @Jacob Gude,

Please confirm that when the JVM arg is unset, Jira is working as expected.

The issue might be caused by special characters in your password causing a malfunction. 

[Jacob Gude]

Thanks for the response. Jira works as expected if JVM arg is unset. I don't have any special characters in pw. Just numbers and letters.

[Edwin Kyalangalilwa]

Are all the necessary java args set?

-Djavax.net.ssl.trustStore="$TRUSTSTORE"
-Djavax.net.ssl.trustStorePassword"=changeit"
-Djavax.net.ssl.keyStore="$KEYSTORE"
-Djavax.net.ssl.keyStorePassword="changeit"

JIRA Does Not Start after Configuring SSL Due to Unspecified TrustStore or Keystore Path

[Jacob Gude]

keystore and password are set. I did not add trustStore. In the google doc it didn't specify to set the trustStore. Just the keystore. 

[Edwin Kyalangalilwa]

Please post some logs from catalina.out or atlassian-jira.log. At the time of startup.

[Jacob Gude]

Thanks for your responses. I was able to fix by recreating certificate and key from Google and creating another .jks file. I'm guessing the first one was corrupt. I was able to connect Google LDAP to our Jira instance.