JIRA Integration with Fisheye Throws ERROR 401

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Symptoms

In JIRA log, two types of errors can be found:

1 2 3 4 http-bio-8080-exec-3 WARN janedoe 711x4983x1 reitw0 53.141.163.97,127.0.0.1 /plugins/servlet/applinks/auth/conf/oauth/outbound/apl-2lo/58b8a734-d679-31ab-bcff-8c81c2991a7c [jirafisheyeplugin.config.fisheye.FishEyeInstanceManagerImpl] Request to 'http://example.host.com/crucible/rest-service-fe/server-v1' failed due to missing OAuth credentials. Assuming FishEye+Crucible both available com.atlassian.applinks.api.CredentialsRequiredException: You do not have an authorized access token for the remote resource. at com.atlassian.applinks.core.auth.oauth.ThreeLeggedOAuthRequestFactoryImpl.retrieveConsumerToken(ThreeLeggedOAuthRequestFactoryImpl.java:93) at com.atlassian.applinks.core.auth.oauth.ThreeLeggedOAuthRequestFactoryImpl.createRequest(ThreeLeggedOAuthRequestFactoryImpl.java:84)
1 2 3 2013-12-09 11:53:44,149 http-bio-8080-exec-16 WARN johndoe 713x5058x5 11no8js 10.20.3.40,127.0.0.1 /rest/tabs/1.0/com.atlassian.jirafisheyeplugin:fisheye-issuepanel/SDENG-10 [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Fexample.host.com%2Fcrucible", oauth_problem="token_rejected"} 2013-12-09 11:54:05,617 http-bio-8080-exec-2 WARN johndoe 714x5076x4 11no8js 10.20.3.40,127.0.0.1 /rest/tabs/1.0/com.atlassian.jirafisheyeplugin:fisheye-issuepanel/SDENG-10 [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Fexample.host.com%2Fcrucible", oauth_problem="nonce_used"} 2013-12-09 11:54:05,654 http-bio-8080-exec-2 WARN johndoe 714x5076x4 11no8js 10.20.3.40,127.0.0.1 /rest/tabs/1.0/com.atlassian.jirafisheyeplugin:fisheye-issuepanel/SDENG-10 [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Fexample.host.com%2Fcrucible", oauth_problem="nonce_used"}

In Fisheye log:

1 2 3 4 5 6 7 8 9 10 11 12 2013-12-09 11:53:26,054 INFO [quartzScheduler_Worker-9 ] fisheye UserSynchroniserJob-execute - Starting resynchronising users 2013-12-09 11:53:26,118 INFO [quartzScheduler_Worker-9 ] fisheye DefaultUserManager-synchroniseUsers - resynchronising users with crowd 2013-12-09 11:53:44,098 ERROR [qtp2015928291-185 ] com.atlassian.sal.fisheye.user.DefaultUserManager DefaultUserManager-resolve - Could not resolve user 'johndoe' 2013-12-09 11:53:44,147 WARN [qtp2015928291-185 ] com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl OAuthProblemUtils-logOAuthProblem - Problem encountered authenticating OAuth client for url "http://example.host.com/crucible/rest-service-fe/search-v1/crossRepositoryQuery", error was "token_rejected", with parameters "{oauth_problem=token_rejected}" 2013-12-09 11:54:01,752 INFO [qtp2015928291-175 ] fisheye DefaultUserManager-importUser - auto-import user: "johndoe" ... 2013-12-09 11:54:05,652 WARN [qtp2015928291-185 ] com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl OAuthProblemUtils-logOAuthProblem - Problem encountered authenticating OAuth client for url "http://example.host.com/crucible/rest-service-fe/search-v1/crossRepositoryQuery", error was "nonce_used", with parameters "{oauth_problem=nonce_used}" 2013-12-09 11:54:05,788 INFO [IncrementalPinger1 SDENG-cloc] fisheye BaseRepositoryScanner-ping - done slurp for /SDENG-cloc time = 231ms 2013-12-09 11:54:26,058 INFO [quartzScheduler_Worker-9 ] fisheye UserSynchroniserJob-execute - Starting resynchronising users 2013-12-09 11:54:26,112 INFO [quartzScheduler_Worker-9 ] fisheye DefaultUserManager-synchroniseUsers - resynchronising users with crowd 2013-12-09 11:54:26,249 INFO [quartzScheduler_Worker-9 ] fisheye DefaultUserManager$24-doInTransaction - 'johndoe' has been deactivated in FishEye.

Diagnosis

  • Same set of user exist in both JIRA and Fisheye and can login to both instance.

  • Crowd SSO is being used in both JIRA and Fisheye.

  • Oauth authentication is used in the application link

  • Only some users face this problem.

  • User Management Synchronisation Interval is set to 1 minute and only partial groups are set to be synchronize as part of the workaround suggested in CWD-2650

Cause

For the newly created users in Fisheye, the OAuth Token was deleted immediately when the synchronisation was running within one minute time.

Solution

Resolution

Ensure that all groups are synchronized via Fisheye Administrations > Authentications

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.