Application Links breaking when setting up SSL Client Certificate (.p12) authentication

[Gregor_Naeckel]

Hi Community,

im trying to set up an SSL Client Certificate based authentication for Jira and Confluence.

While logging-in is working so far, it is breaking the Application Link between Jira and Confluence. It returns a 400: Bad Request Error, e.g. the same Error as if you were to Login to either app without an SSL Certificate.

It there any way to get the App Links working again?

Environment: Jira and Confluence as Docker Containers and Nginx as reverse proxy

Any help is appreciated - Thank you in advance!

Gregor

[Gregor_Naeckel · Accepted solution]

Whoever might need this - i used these instructions and got it working:
https://r-pufky.github.io/docs/services/nginx/cert-based-authentication.html

It is actually the normal way to set up something like this - my problem was that due to the usage of Docker, the node IPs communcated over the gateway and not their actual IP adresses.

Allowing those IPs or putting the whole internal range into the nginx geo module did the trick at the end.

Cheers,

[Thiago Masutti]

Hi @Gregor_Naeckel 
Welcome to the Atlassian Community.

You might want to take a look at this KB article: https://confluence.atlassian.com/jirakb/application-links-not-working-behind-third-party-sso-962336266.html 

Although it mentions SSO, the concept might be the same as you probably need to allowlist requests made between the backend nodes.

Kind regards,
Thiago Masutti

[Gregor_Naeckel]

Hi Thiago,

thank you for the reply.

Unforunately, allowlisting these URLs in both backend nodes did not do the trick. :(

Best,
Gregor