SSL Help - Confluence and JIRA Application Links

Adam White September 19, 2013

I need help getting JIRA and Confluence talking to each other via SSL. When I connect to either of the sites, I get the usual Untrusted Identity warnings because they are not from a CA. I think the piece that I am missing here is a root-level or a faked trust.

Background/Information: JIRA, Confluence, (and eventually Fisheye) are all behind our corporate firewall. I will be sanitizing the URLS for the purposes of this post:

JIRA'S Base URL is: https://dev-server:8443/jira

Confluence's Base URL is: https://dev-server:8444/confluence

The keystore was generated using Portecle and is located in the JIRA home directory. I am not using the java home keystore to do this.

The keystore looks like this:

Keypair #1: Alias Name: JIRA CN: https://dev-server:8443/jira

Keypair #2: Alias Name: Confluence CN: https://dev-server:8444/confluence

Trust cert: Alias: JIRA --- This was generated by basically saving the keypair cert in #1 and importing it as a trusted cert… I think this is where I went wrong.

I also tried to import a Trust Reply, but I think that was messed up as well.

Any ideas here? I’m sure I left some details out.

1 answer

1 accepted

0 votes
Answer accepted
Janet Albion
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 19, 2013

I am suspecting a bug https://jira.atlassian.com/browse/JRA-34550 that is affecting instance running on HTTPS that is not using the default port 443 .

Adam White September 19, 2013

Will running confluence on the same port interfere with JIRA? I have them set to use different context paths (/JIRA) and (/Confluence).

Janet Albion
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 22, 2013

Adam,

If JIRA and Confluence are running on different server, yes you can use the same port 443. But, if they are on the same server, we would recommend using web server as a workaround.

You may refer to the Workaround section in the bug to find more detail on it

Suggest an answer

Log in or Sign up to answer