We have our test environment setup as follows:
JIRA and Confluence are setup on the same server box. Thus both apps will share their machine's ip (except for the port numbers are).
I've configured on application links on both apps, setting up trusted applications, and they're configured properly - no issues.
However when trying to test this, I logged onto Confluence, created a page, go to Insert -> Jira Issue, I could not find any JIRA issues in the dropdown list.
I looked up the atlassian-confluence.log file, and I found this line.
WARN anonymous 871x6512x1- xxxxxxx /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml [auth.trustedapps.filter.TrustedApplicationFilterAuthenticator] Failed to login trusted application: confluence 9123435 due to: com.atlassian.security.auth.trustedapps.InvalidCertificateException: Request not allowed to access URL: /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml
I set the URL Pattern configuration settings for JIRA as folllows:
/plugins/servlet/streams, /sr/jira.issueviews:searchrequest, /secure/RunPortlet, /rest, /rpc/soap,
I still could not understand why it doesn't work despite the above setup. And I can confirm that our JIRA's database is prepoulated with lots of JIRA issues so the database could not be empty.
So what's wrong with our trusted authentication setup? Any ideas??
I found the fix to this issue.
Apparently, there's a separate installation guide for integrating JIRA and Confluence seamlessly.
So I had to uninstall and reinstall both our JIRA and Confluence, reinstalled the CORRECT versions as per the above link. (formerly, JIRA 5.1.1 and Confluence 4.2.11) and now it works again.
It's also works with our JIRA's production data copy on our JIRA Eval database too - so it's all looking good now!
Thanks for the help
invalid HTTPS? I didn't realise HTTPS protocol is part of the JIRA/Confluence setup. I couldn't find it anywhere in the documentation?
Where in JIRA can I find the HTTPS configuration settings?
No I didn't. And our JIRA is hosted internally - meaning it's for private access, not public access.
We didn't configure JIRA to use HTTPS for internal use either.
We're using an evaluation licence for Confluence, whilst our JIRA server installation is a copy of our production JIRA server. We're currently in the process of evaluating the latest JIRA software version before making decision to buy it.
We have similar setup like yours and we use Crowd to get users from Active Directory. I use internal Crowd users and groups to help manage non-AD users, like dedicated accounts for application links. My experience with setting up application links(Without using Crowd):
Hope this helps.
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