Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Test basic connection : Failed The following URL does not specify a valid Crowd User Management REST

dummy September 13, 2018

After changing the base domain in Confluence, Jira and Bitbucket as well as in Crowd from myold.com to mynew.com, we get an error when testing the Remote Directory Connection from Confluence to Crowd:

Test basic connection : FailedThe following URL does not specify a valid Crowd User Management REST service: http://crowd.mynew.com/crowd/rest/usermanagement/1/search?entity-type=user&start-index=0&max-results=1&expand=user

How could this be fixed please?

Directory summary from Confluence:

=== Current user ===
Directory ID: 294914
Username: ralf
Display name: Ralf L...
Email address: r.l.....@mynew.com

=== Directories configured ===
Directory ID: 294913
Name: Confluence Internal Directory
Active: true
Type: INTERNAL
Created date: 2015-02-09 19:56:08.268
Updated date: 2015-02-09 19:56:08.268
Allowed operations: [UPDATE_USER, UPDATE_GROUP, CREATE_GROUP, UPDATE_ROLE, UPDATE_GROUP_ATTRIBUTE, CREATE_USER, UPDATE_USER_ATTRIBUTE, CREATE_ROLE, UPDATE_ROLE_ATTRIBUTE, DELETE_GROUP, DELETE_USER, DELETE_ROLE]
Implementation class: com.atlassian.crowd.directory.InternalDirectory
Encryption type: atlassian-security
Attributes:
"user_encryption_method": "atlassian-security"

Directory ID: 294914
Name: Crowd Server
Active: true
Type: CROWD
Created date: 2015-02-09 20:11:54.926
Updated date: Thu Sep 13 15:27:18 CEST 2018
Allowed operations: [UPDATE_USER_ATTRIBUTE, UPDATE_GROUP_ATTRIBUTE]
Implementation class: com.atlassian.crowd.directory.RemoteCrowdDirectory
Encryption type: null
Attributes:
"application.name": "confluence"
"application.password": ********
"com.atlassian.crowd.directory.sync.issynchronising": "false"
"com.atlassian.crowd.directory.sync.lastdurationms": "112"
"com.atlassian.crowd.directory.sync.laststartsynctime": "1536845237893"
"crowd.server.url": "http://crowd.mynew.com/crowd/"
"crowd.sync.incremental.enabled": "true"
"directory.cache.synchronise.interval": "600"
"useNestedGroups": "true"

 

One more weird detail:

With "crowd.server.url": "http://crowd.myold.com/crowd/" Jira is working. With "crowd.server.url": "http://crowd.mynew.com/crowd/" Jira doesn't work. So Jira behaves similar as Confluence.

But Bitbucket is working with "crowd.server.url": "http://crowd.mynew.com/crowd/".

 

The hostname crowd.mynew.com is resolved to a separate proxy in the LAN, which is redirecting http to https.

1 answer

0 votes
Philip Lewis November 5, 2020

Hey, I was having the same error having set up crowdId server. At first it was working when I used the http://localhost:port/ form of the url but when I reconfigured it to use a proxied url equivalent to your crowd.mynew.com I got the exact same error as you - funnily enough your last comment about redirecting to https at the proxy set me on the right track. I changed all the urls in the crowd.properties file to use https instead of http and it all works now so you kind of answered your own question but helped me into the fact. Thanks for helping me and here is your answer :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events