Unable to Start Confluence after LDAP Integration
Symptoms
Confluence is unable to start after configuring the atlassian-user.xml for LDAP integration.
The following stack trace appears in atlassian-confluence.log:
Caused by: java.lang.RuntimeException: Atlassian User failed to initialize: Unable to load atlassian-user configuration: org.dom4j.DocumentException: Error on line 33 of document : The entity name must immediately follow the '&' in the entity reference. Nested exception: The entity name must immediately follow the '&' in the entity reference.
at com.atlassian.user.configuration.xml.XMLConfiguration.getDelegationAccessor(XMLConfiguration.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Cause
There is at least an LDAP mapping property value that contains unescaped ampersands ("&"). As per atlassian-user.xml reference:
If these values contain ampersands, they must be escaped in the XML file. This is a common situation
with LDAP search filters and passwords containing ampersands. For example, the LDAP search filter
&(objectClass=user)(mail=*@example.com)) would be put in the
XML as: <userSearchFilter>(&(objectClass=user)(mail=*@example.com))</userSearchFilter>
Resolution
Escape any ampersands ("&") by replacing them with
&
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.