I purchased a cert from a CA and am trying to set up both Confluence and JIRA instances on the same machine to be accessible in this manner:
The FQDN is the same for both instances, but the port numbers are different, so this should work.
I have followed the documentation for both Confluence and JIRA to get them running over SSL using a cert from a CA.
I created the .keystore file and copied it to <CONFLUENCE-INSTALL>mykeystore.jks, and Confluence is accessible. (Yes, I edited the <CONFLUENCE-INSTALL>conf/server.xml with the keystore path to <CONFLUENCE-INSTALL>mykeystore.jks, the SSl port for Confluence, and keystore password.)
I then made a copy of mykeystore.jks and placed it into <JIRA-INSTALL>mykeystore.jks and edited the <JIRA-INSTALL>/conf/server.xml to have the keystore path of <JIRA-INSTALL>mykeystore.jks, the SSL port for JIRA, and the keystore password.
However when I try to access JIRA, it doesn't load. I can only get JIRA to load using a self-signed cert.
I'm not very familiar with keystore files, but shouldn't it be possible to use the same SSL cert on the same machine? I mean, I'm using two different instances and two different ports (9443 and 8443) for each instance.
Any advice to help in what I'm trying to do (both JIRA and Confluence on same machine assessible via same FQDN but using different ports) would be appreciated.
For others who may encounter the same issue:
I determined the issue was the "Key Alias" parameter setting in JIRA's in server.xml. (Confluence does not have a Key Alias parameter in it's server.xml, so it went unnoticed.)
Once I updated JIRA's server.xml key alias parameter to the key alias I used when going through the keystore methods, JIRA started working.
Also note that when using JIRA and Confluence from the same FQDN/domain name, you will inadvertently log yourself out of one application anytime you interact with another application, as long as you are using the same browser and in a non-incognito mode. Reason: cookies. Cookies do not specify the port number, so one cookie from one application tied to the FQDN will overwrite the cookie from the other application (also tied to the FQDN).
There are two ways to solve this problem:
1. Edit context path (I opted to NOT do this one),
2. Edit either JIRA or Confluence to use a different cookie name. (I chose to edit JIRA).
1. Change the session cookie name by adding the following line to your JAVA_OPTS parameter (found here: <install>/bin/setenv.sh):
and (if you are using Tomcat v7, which you probably are)
2. add the following code in
<install>/conf/context.xml by setting the value for sessionCookieName
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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