User directories health check

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

The user directories health check ensures that a connection between Jira and supported user directories can be established in a healthy manner. Only enabled user directories are tested by this health check.

Currently, the health check supports two types of user directories:

  • LDAP

  • Crowd

Solution

Understanding the results

In the following tables, learn how to interpret the results of the health check for LDAP and Crowd.

LDAP

Indicator

Result

Interpretation

✔️ Pass

No supported user directories were found.

Currently, there are no enabled or configured LDAP user directories.

✔️ Pass

The provided LDAP credentials are valid.

The connection between Jira and a user directory can be established and authentication has been successful.

⚠️ Warning

The connection to the LDAP server can't be established.

The connection between Jira and an LDAP user directory can’t be established.

Error

The provided credentials were rejected by the LDAP server <user_directory_name>. Checks if the user and password provided by the user directory configuration to access the LDAP server are valid.

The connection between Jira and an LDAP user directory can be established but the authentication process has failed.

Crowd

Indicator

Result

Interpretation

✔️ Pass

No supported user directories were found.

Currently, there are no enabled or configured Crowd user directories.

✔️ Pass

The provided Crowd credentials are valid.

The connection between Jira and a user directory can be established and authentication has been successful.

⚠️ Warning

The connection to the Crowd server can't be established.

The connection between Jira and a Crowd user directory can’t be established.

Error

The credentials provided were rejected by the Crowd server. Check if the user and password provided by the user directory configuration to access the Crowd server are valid.

The connection between Jira and a Crowd user directory can be established but the authentication process has failed.

What happens when I ignore the warning?

If a connection to a user directory can’t be established or the authentication process is failing, users won’t be able to access the authentication service. Depending on the authentication directory order and the availability of other directories, they might encounter issues while trying to log in to the application or won’t be able to refresh their authentication token, thus losing the ability to interact with the application.

Troubleshooting

Authentication failure

Go to your user directory configuration and confirm that provided user and password are valid.

Connectivity failure

Check the connection and healthiness of the machine that the user directory is running on. To review common LDAP user directory issues, reference Common user management errors.

Updated on April 10, 2025

Still need help?

The Atlassian Community is here for you.