Connection to Crowd Fails due to URI-Reference required

Summary

Symptoms

1. Crowd users are unable to authenticate.

2. Adding users to Crowd directory fails.

3. Synchronisation fails.

The following appears in the atlassian-jira.log:

Diagnosis

1. Ensure that the OS user that start-up JIRA has the necessary permission to read JIRA's crowd.properties.

2. Ensure that the atlassian-jira/WEB-INF/classes/crowd.properties file is complete and contain valid entries, as in The crowd.properties file documentation.

3. Run the following SQL:

   1 SELECT d.directory_name, a.* FROM cwd_directory d JOIN cwd_directory_attribute a on d.id=a.directory_id WHERE d.directory_type='CROWD';

   It should return the following records. If it does not, please see the resolution section below.

   1 2 3 4 5 6 7 8 9 directory_name | directory_id | attribute_name | attribute_value ----------------+--------------+---------------------------------------------------------+-------------------------- Crowd Server2 | 10100 | com.atlassian.crowd.directory.sync.lastdurationms | 65 Crowd Server2 | 10100 | com.atlassian.crowd.directory.sync.laststartsynctime | 1313453356673 Crowd Server2 | 10100 | com.atlassian.crowd.directory.sync.currentstartsynctime | Crowd Server2 | 10100 | useNestedGroups | true Crowd Server2 | 10100 | application.name | jiraci Crowd Server2 | 10100 | application.password | admin Crowd Server2 | 10100 | crowd.server.url | http://derpydoo:6095/crowd

Cause

Some of the possible causes are:

1. The server hosting Crowd has changed.

2. An old crowd.properties file was used during the upgrade.

3. There were recent network configuration changes.

4. JIRA's crowd.properties is not accessible by JIRA user

Solution

Resolution

Recommended:

1. Ensure that JIRA user has full permission to its crowd.properties

2. Disable the Crowd Authenticator SSO, as in our Configure JIRA to use Crowd's Authenticator to enable SSO.

3. Log into JIRA using a Local Administrator user in the JIRA Internal Directory.

4. Recreate the connection as described in our Connecting to Crowd or Another JIRA Server for User Management documentation.

If you do not have internal admin access to JIRA, try the following:

1. Copy the below SQL into a text editor.

   1 2 3 4 5 6 INSERT INTO cwd_directory_attribute values (10101,'application.name','jira'); INSERT INTO cwd_directory_attribute values (10101,'application.password','jirapass'); INSERT INTO cwd_directory_attribute values (10101,'crowd.server.url',' http://172.27.1.21:8095/crowd/services'); INSERT INTO cwd_directory_attribute values (10101,'crowd.sync.incremental.enabled','false'); INSERT INTO cwd_directory_attribute values (10101,'directory.cache.synchronise.interval',3600); INSERT INTO cwd_directory_attribute values (10101,'useNestedGroups','false');

2. Replace the id 10101 with the id returned in the SQL from the diagnosis section.

3. Replace the server URL, application name and password appropriately. If you're unsure what values they should be, recreate the links using the first resolution or raise a ticket on support.atlassian.com.

4. Back up the database.

5. Execute the SQL update.