9 November 2015

We've deprecated this Diagnostics Plugin guide, because the Diagnostics Plugin has been removed from the Atlassian Marketplace and is no longer being actively developed.

But there's good news! We've released a whole better diagnostics experience for application links. You get the new application links diagnostics with the recent version of Atlassian products.

Some teasers...

Built-in

The new diagnostics experience is built in to the Application Links plugin, so is available right out of the box.
You don't have to install or maintain a separate plugin.

Full product support

The new diagnostics experience supports all Atlassian products that use application links, including Jira 7 and Bamboo
(neither of which are supported by the old Diagnostics Plugin).

If you're having trouble with application links, see our Application Links troubleshooting guide.

 

 

Overview

This test verifies that the diagnostic tool is able to access a resource on the remote application, via each type of application link authentication that has been configured. This resource is accessible only by an administrator or system administrator, so this test works only if you are an administrator on both sides of the application link.

Understanding the Results

IconText resultWhat this means
SUCCESSThe test was successful.
WARNINGSome of the component tests failed and needs troubleshooting.
FAILThe test was not successful and needs troubleshooting.

Troubleshooting

Authentication Test

  • URL path tested: <URL>/rest/applinks/1.0/applicationlink
Error(s)Steps to Resolve
  • Failed to authenticate against <Application Link>
  • Can you log into the target instance?
  • Can you access that URL through a browser?
  • Is there anything between the applications, for example proxy / firewall and/or load-balancer? If so, verify the configuration is correct.
  • Is SSO used? If so, verify the configuration is correct.
  • Disabling the proxy and/or SSO can effectively isolate whether or not it is at fault.
  • Failed to authenticate against <Application Link> using: OAuthAuthenticationProvider
  • If there is a 401 error in the Diagnostics tab for this provider, it could be:
    • You need to authorise the application to obtain a valid oauth token. A link is being added to result to provide this automatically when this error occurs in a future release of the plugin.
    • You have a valid oauth token for a user in the other application who does not have administrator access. Log in to the other application, and revoke the oauth token in that user's profile, then authorise again using a user with administrator access.
  • Failed to authenticate against <Application Link> using: TwoLeggedOAuthAuthenticationProvider
  • If there is a 401 error in the Diagnostics tab for this provider it could be caused by:
    • In the remote side of the link, there is no user configured in the incoming authentication for two-legged oauth. This is a completely valid configuration, and in this case the authentication failure can be ignored.
    • In the remote side of the link, the user configured either does not exist, or does not have administrator access. Either change the user in the two-legged oauth incoming authentication to be an administrator, or grant that access to the existing user.

Basic Checks

Error(s)Steps to Resolve
  • Application Link is NULL
  • The Application Link has been corrupted, please recreate it.
  • Application URL is NULL
  • This means the application URL is empty. Try to edit the link and see if this can be fixed.
  • This shouldn't happen, the Application Link will probably need to be recreated.

Providing Information to Support

Atlassian applications allow the use of reverse-proxies within our products, however Atlassian Support does not provide assistance for configuring them. Consequently, Atlassian can not guarantee providing any support for them.

If assistance with configuration is required, please raise a question on Atlassian Community.

In case you are unable to troubleshoot and fix the problem by yourself, please create a support ticket at support.atlassian.com and attach the following information to the ticket:

  1. Copy and save the contents of the 'Diagnostics' tab as a text file.

  2. Screenshots of the Application Links configuration.

  3. A Support ZIP.

Unknown macro: {dynamiccontentbylabel}

 




 

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.