JIRA Fails to Start after LDAP Configuration
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
After configuring osuser.xml with values taken from a successful test from the LDAP configuration wizard, JIRA will not start. Logs contain errors like:
1
2
3
4
2010-09-10 11:32:41,327 main ERROR [opensymphony.user.util.ConfigLoader] Could not parse config XML
org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
Cause
There is an & or illegal character, likely in the password.
Resolution
Remove any non-alphanumeric characters from the password or other fields.
ℹ️Please see our Troubleshooting LDAP User Management documentation for further assistance with diagnosing LDAP problems.
Was this helpful?