nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Applink to Jira fails

Horst Runkel

Hi,

I have an issue with confluence 7.14.1 and Jira (latest release as far as I am aware). After an update the app link broke and is erroring with "configuration error". The confluence server is complaining about an expired cert. I have been looking high and low, turned any cert-store over, but cannot find any cert with that expiry date. Anyone knows the mechanisms and where to look for the cert in question?

Much appreciated.......

Accepted answers

All comments

Nic Brough -Adaptavist-

Welcome to the Community!

Application links work best when they are two-way, so Jira needs to be able to talk to Confluence, and Confluence to Jira.

SSL is usually done bi-directionally, so both ends of a link will need a certificate to go talk to the other.

So, to answer the "where is the cert" part of the question - you need to be looking in the key-stores that both your Jira and Confluence are using.

If you are getting an error when putting a link to Jira into your Confluence server, then I suspect you're looking in the right place already - the key-store for Confluence.

One thing to be aware of though is that the expiry date you get in the error message may not always be the expiry date of the cert you are looking for.

I would not actually be that worried about the expired cert message, I would go for the more simple approach of simply generating new certificates and installing them. The exact cert that no longer works is not that important - the fix is probably going to be to install a new one, whatever the error is.

Kishan Sharma

Hi @Horst Runkel Welcome to the Atlassian Community!!!

Supplementing to Nic's answer, If your application links have stopped working after a recent upgrade it's possible that your customizations to the application's server.xml file were overwritten. Custom changes can include reverse proxy configuration and HTTPS configuration. You should check that the upgraded server.xml file matches the pre-upgrade server.xml.

You can also refer this KB article to see if you are seeing the similar errors in the application logs and if yes, follow the resolution mentioned on it. Let me know if that helps.

Horst Runkel

Hi,

thanks for the suggestions. The certs are held by a load balancer in front of them - and they are still valid; the server.xml was safed and restored from the working setting. Initially the issue was an interim cert, but that was rectified with a replacement.

I am going to dig a bit more.

Horst Runkel

Should have answered in here:

Hi,

Horst Runkel

Thanks, the certs are held on a loadbalancer and they work fine according to openssl. There was an issue with expired intermediate, but that has solved.

Horst Runkel

Further to above answer:

I have redeployed server.xml and restarted confluence, which brought all back into line.

Kishan Sharma

Great that it worked for you 😀

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server

jira