LDAP Troubleshooting Resources
If the above resources don't help, continue below.
Problems During Initial Setup
Open a Support Ticket and include:
- Refer to Troubleshooting LDAP User Management. Run the tests and paste the output in your support ticket.
- Download an LDAP browser to make sure you've got the right values. Atlassian recommends LDAP Studio. Include screenshots of your user and group DN's.
- Attach your
atlassian-user.xml file.
Complex Authentication or Performance Problems
Open a Support Ticket and include:
Confluence server
- Take a screenshot of Confluence's
Administration → System Information (or save the page as HTML)
- Take a screenshot of Confluence's
Administration → Global Permissions, if you are having problems with logging in
- Take a screenshot of the Space permissions page, if you are having problems with space or page permissions.
Confluence configuration files
- Attach a copy of
atlassian-user.xml, found in confluence/WEB-INF/classes
- Attach a copy of
osuser.xml, found in confluence/WEB-INF/classes.
- If you have implemented a custom authenticator or in any way modified
seraph-config.xml or seraph-paths.xml, please provide the modified files as well.
User management system
- What is the name and version of your LDAP server?
- Does your LDAP server use dynamic or static groups?
Using Active Directory for LDAP?
Please include LDAP Studio Entry Editor snaphots with the information specified on this page
Diagnostics
- Enable profiling (as described here)
- Enable detailed user management logging by editing
confluence/WEB-INF/classes/log4j.properties:
Change this section:
###
# Atlassian User
###
#log4j.logger.com.atlassian.user=DEBUG
#log4j.logger.com.atlassian.confluence.user=DEBUG
#log4j.logger.bucket.user=DEBUG
|
To this:
###
# Atlassian User
###
log4j.logger.com.atlassian.user=DEBUG
log4j.logger.com.atlassian.confluence.user=DEBUG
log4j.logger.bucket.user=DEBUG
|
- After enabling both the above, please attempt a Confluence LDAP account login and attach a copy of the log files that are produced when the problem occurs. To do this, locate your install directory or exploded WAR directory, then zip the full /logs subdirectory into a single file for us to examine. An example location might be confluence-2.2.2-std/logs.