Application Links and Trusted Applications Troubleshooting

Still need help?

The Atlassian Community is here for you.

Ask the community

Portlets have been deprecated in JIRA 4.0. If you're upgrading to JIRA 4.x, consider a tandem upgrade to a Confluence version that supports gadgets, then change the jiraportlet macros to use gadgets instead. See Migrating from JIRA Issues and JIRA Portlets to Gadgets.

tip/resting Created with Sketch.

 Please ensure that you are not running multiple Atlassian applications in a single Tomcat container. See this FAQ for more information.


JIRA Integration

Below are the warning messages which may appear on your Confluence page, above the output of the JIRA Issues macro. Make sure to check the JIRA Integration FAQ.

Warning Message

Cause

Solution

Warning Message Can be Turned Off?

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

JIRA is running over SSL

Add JIRA's SSL Certificate to the Java Keystore

No

The JIRA server does not recognise your user name. Issues have been retrieved anonymously.

The logged-in Confluence user is not registered in the JIRA user base.

Add the username to your JIRA user base. It is highly recommended that your JIRA and Confluence instances share a common user base.

No

The JIRA server does not trust this Confluence instance for user authentication. Issues have been retrieved anonymously. You can set the macro to always use an anonymous request by setting the 'anonymous' parameter to 'true'.

Your JIRA instance has not been configured to trust your Confluence instance.

One of the following solutions:

Yes

The JIRA server does not support trust requests. Issues have been retrieved anonymously. You can set the macro to always use an anonymous request by setting the 'anonymous' parameter to 'true'.

Your JIRA instance is not able to handle trusted communications (i.e. the JIRA version is earlier than 3.12.0).

One of the following solutions:

Yes

Failed to login trusted application: confluence:14159892 due to: com.atlassian.security.auth.trustedapps.CertificateTooOldException: OLD_CERT; Certificate too old.

There is a date/time difference between the JIRA server and Confluence server.

-

Primarily, JIRA is set up to trust Confluence, unless you are using the Applinks plugin.

Database

The entries are stored on the trustedapp table in JIRA and the KEYSTORE table in Confluence. These entries should match, if there is a trust in place. One common troubleshooting approach is to truncate these tables and begin again.

Confluence Knowledge Base

JIRA Knowledge Base

Open Bugs and Features in the Confluence Project in JIRA Bug Tracker

type key summary assignee reporter priority status resolution created updated due

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

Open Bugs and Features in the JIRA Project in JIRA Bug Tracker

type key summary priority status

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

Last modified on Nov 16, 2018

Was this helpful?

Yes
No
Provide feedback about this article

In this section

Powered by Confluence and Scroll Viewport.