Outgoing authentication shows 404 error message via Application Links configuration

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.

Problem

When JIRA integrate with Atlassian applications (such as Bamboo, Bitbucket or Confluence), it's showing 404 error message below via Outgoing Authentication dialog on the Bamboo application:

Oops, you've found a dead link

Sometimes, you will get the following stack traces in the atlassian-jira.log:

 ___ FAILED PLUGIN REPORT _____________________
    
    'com.atlassian.applinks.applinks-basicauth-plugin' - 'Applinks - Plugin - Basic Authentication'  failed to load.
    		Application context initialization for 'com.atlassian.applinks.applinks-basicauth-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)(objectClass=com.atlassian.applinks.api.ApplicationLinkService)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor))
...
	'com.atlassian.applinks.applinks-cors-plugin' - 'Applinks - Plugin - CORS'  failed to load.
    		Application context initialization for 'com.atlassian.applinks.applinks-cors-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)(objectClass=com.atlassian.applinks.api.ApplicationLinkService)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor))
...
   	'com.atlassian.applinks.applinks-trustedapps-plugin' - 'Applinks - Plugin - Trusted Apps'  failed to load.
    		Application context initialization for 'com.atlassian.applinks.applinks-trustedapps-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)(objectClass=com.atlassian.applinks.api.ApplicationLinkService)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor))
...    
    'com.atlassian.applinks.applinks-oauth-plugin' - 'Applinks - Plugin - OAuth'  failed to load.
    		Application context initialization for 'com.atlassian.applinks.applinks-oauth-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)(objectClass=com.atlassian.applinks.spi.link.MutatingApplicationLinkService)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)(objectClass=com.atlassian.applinks.spi.manifest.ManifestRetriever))
...
2016-03-13 08:32:35,089 xxx Timer ERROR      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.applinks.applinks-basicauth-plugin], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)] (from bean [&authenticationConfigurationManager]), Dependency on [(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)] (from bean [&typeAccessor]), Dependency on [(objectClass=com.atlassian.applinks.api.ApplicationLinkService)] (from bean [&applicationLinkService])
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.applinks.applinks-basicauth-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)(objectClass=com.atlassian.applinks.api.ApplicationLinkService)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor))
	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
	at java.util.TimerThread.mainLoop(Timer.java:555)
	at java.util.TimerThread.run(Timer.java:505)
2016-04-19 15:54:02,002 ajp-nio-8009-exec-29 ERROR xxx xx xx xxxx /plugins/servlet/applinks/listApplicationLinks [o.a.c.c.C.[Catalina].[localhost].[/]] Unhandled exception occurred whilst decorating page
java.lang.NullPointerException: Plugin container accessor is null. Plugin: com.atlassian.applinks.applinks-cors-plugin. Module name: com.atlassian.applinks.cors.auth.CorsAuthenticationProviderPluginModule.
	at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:250)

Diagnosis

Environment

  • Affected JIRA 7.1.0 and 7.1.1

Diagnostic Steps

  • Scan JIRA logs (via $JIRA_HOME/log) and ensure the errors above is not showing up. 
  • Scan application.xml (via JIRA Support Zip/application-properties) and check if you find this:

    <plugin>
          <key>com.atlassian.applinks.applinks-oauth-plugin</key>
          <name>Applinks - Plugin - OAuth</name>
          <version>5.0.6</version>
          <vendor>Atlassian</vendor>
          <status>DISABLED</status>
          <vendor-url>http://www.atlassian.com/</vendor-url>
          <framework-version>2</framework-version>
          <user-installed>false</user-installed>
          <bundled>Bundled</bundled>
    </plugin>

Cause

Some JIRA application links core plugins was not started or enabled successfully such as:

  1. Applinks - Plugin - Basic Authentication
  2. Applinks - Plugin - CORS
  3. Applinks - Plugin - Trusted Apps
  4. Applinks - Plugin - OAuth

Resolution

  • Increase plugin timeout during JIRA startup for the plugins to enabled.
  • If increasing plugin time does not help the case, you may enable the following plugins through UI via Manage Add-ons > choose System (dropdownlist)
    1. Applinks - Plugin - Basic Authentication
    2. Applinks - Plugin - CORS
    3. Applinks - Plugin - Trusted Apps
    4. Applinks - Plugin - OAuth
Last modified on Nov 15, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.