Platform Notice: Server only. This article only applies to Atlassian products on the Server platform.

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

Problem

JIRA/Crowd Authentication configuration fails and the following appears in the atlassian-fisheye.log:

2014-12-01 10:01:32,879 WARN  [qtp1261031890-182 ] org.apache.commons.httpclient.HttpMethodDirector HttpMethodDirector-processWWWAuthChallenge - Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flocalhost%3A8080"}
2014-12-01 10:01:32,883 ERROR [qtp1261031890-182 ] fisheye DefaultUserManager-getAuthGroupNames - Error listing groups for authentication service: crowd. Problem communicating with Crowd. External groups not included.
com.cenqua.fisheye.user.AuthenticationException: Problem communicating with Crowd
(...)
Caused by: com.atlassian.crowd.exception.InvalidCrowdServiceException: The following URL does not specify a valid Crowd User Management REST service: http://localhost:8080/jira/rest/usermanagement/1/search?entity-type=group&start-index=0&max-results=-1

Diagnosis

• Check the JIRA User Server is configured with an IP it can connect to.
• Check Fisheye can connect to the JIRA URL specified.

Cause

• JIRA URL set in Fisheye's JIRA/Crowd Authentication configuration is incorrect or not reachable. One of the possible condition may apply:
  • The URL doesn't match JIRA's base URL
  • There is a firewall preventing requests to JIRA from the Fisheye server

Resolution

1. Confirm what is the correct JIRA Base URL and make sure it is accessible from the Fisheye server.
2. Go to Fisheye's Administration >> Authentication >> JIRA/Crowd Authentication and click in Edit.
3. Change the JIRA Base URL, specifying the correct URL.
4. Click in Next, then Save.