Bamboo cannot authenticate with JIRA or Crowd (as a user repository)
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
Symptoms
Bamboo cannot authenticate using JIRA as a user repository and throws this error:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
2012-12-05 14:02:46,348 INFO [main] [UpgradeLauncher] Initialisation completed.
2012-12-05 14:02:46,864 ERROR [main] [DefaultUserAccessor] Error in getUser():com.atlassian.crowd.exception.InvalidCrowdServiceException: The following URL does not specify a valid Crowd User Management REST service: http://gojira/crowd/rest/usermanagement/1/search?entity-type=group&start-index=0&max-results=-1
com.atlassian.user.EntityException: com.atlassian.crowd.exception.InvalidCrowdServiceException: The following URL does not specify a valid Crowd User Management REST service: http://gojira/crowd/rest/usermanagement/1/search?entity-type=group&start-index=0&max-results=-1
at com.atlassian.crowd.integration.atlassianuser.UserGroupCache.fetchAndSetSnapshot(UserGroupCache.java:107)
at com.atlassian.crowd.integration.atlassianuser.UserGroupCache.get(UserGroupCache.java:143)
at com.atlassian.crowd.integration.atlassianuser.CrowdUserManager.getUser(CrowdUserManager.java:26)
at com.atlassian.user.impl.delegation.DelegatingListUserManager.getUser(DelegatingListUserManager.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.atlassian.crowd.integration.atlassianuser.DynamicDelegationAccessor$DelegatingInvocationHandler.invoke(DynamicDelegationAccessor.java:115)
...
Caused by: com.atlassian.crowd.exception.InvalidCrowdServiceException: The following URL does not specify a valid Crowd User Management REST service: http://gojira/crowd/rest/usermanagement/1/search?entity-type=group&start-index=0&max-results=-1
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.executeCrowdServiceMethod(RestExecutor.java:418)
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:304)
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchGroupNames(RestCrowdClient.java:545)
at com.atlassian.crowd.integration.atlassianuser.UserGroupFetcher.fetch(UserGroupFetcher.java:38)
at com.atlassian.crowd.integration.atlassianuser.UserGroupCache.fetchAndSetSnapshot(UserGroupCache.java:87)
... 41 moreCause
JIRA or Crowd is unreachable at the configured URL (may also be caused by temporary unavailability of Crowd or Jira).
The URL that is used for JIRA or Crowd server is wrong.
Resolution
Make sure to use a correct URL while configuring Bamboo to switch to using JIRA or Crowd as a user repository. An example that that cause to the above mentioned error is using 'crowd' context path in the JIRA (or Crowd) URL in the BAMBOO_HOME/xml-data/configuration/crowd.properties file:
1
2
3
4
..
application.login.url http://_jira_hostname_:8080/crowd/console/
crowd.server.url http://_jira_hostname_:8080/crowd/services/
...If there is no 'crowd' context path configured for the JIRA server that Bamboo tries to connect, then the URLs should look like this:
1
2
3
4
..
application.login.url http://_jira_hostname_:8080/console/
crowd.server.url http://_jira_hostname_:8080/services/
...Was this helpful?