I have a problem creating trusted communication between JIRA and Confluence. The setup is the following:
All applications use the AJP connector and Apache does the SSL handling.
I was able to configure an application link from Confluence to JIRA using Trusted Applications for the in- and outgoing authentication.
However, the application link in JIRA to Confluence is using Trusted Applications for the out-going authentication only. The incoming authentication is OAuth.
As I understand it this looks normal so far, right? After all JIRA is using only a subset of the users in Confluence and according to the diagram on http://confluence.atlassian.com/display/DOC/Configuring+Authentication+for+an+Application+Link OAuth is the only way JIRA can handle the incoming authentication from Confluence. Is this correct?
The curious thing is: If I try to configure Trusted Applications as the incoming authentication method in JIRA I get the error: Unable to retrieve the application's certificate: Invalid response code of 500 returned from: https://wiki.xyz.ch/admin/appTrustCertificate.
Thanks in advance,
Thomas
Ok, it turns out that if JIRA uses only a subset of the Confluence userbase, it is still possible to establish an Application Link between JIRA and Confluence using Trusted Application authentication.
The problem had to do with the keystore as described in the knowledgebase article: Cannot Add JIRA as a Trusted Application Due to Multiple Trusted Applications. The solution to the problem is described on that page as well.
Many thanks to Septa Cahyadiputra from the Atlassian Support Team for helping to solve the problem!
@Thomas Wendel - Thanks for taking the time to come back and answer your post with the results from Atlassian Support - way too many times it's not done
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.