LDAP Troubleshooting Resources

If the above resources don't help, continue below.

初回セットアップ時の問題

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.

複雑な認証またはパフォーマンスの問題

Open a Support Ticket and include:

Confluence Server

  • Confluence の Administration → System Information のスクリーンショットを取得 (またはページを 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?
  • LDAP サーバーが動的または静的グループを使用していますか?

Using Active Directory for LDAP?

Please include LDAP Studio Entry Editor snaphots with the information specified on this page

診断

  • 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, confluencelog
#log4j.additivity.com.atlassian.user=false
#log4j.logger.com.atlassian.confluence.user=DEBUG,console
#log4j.additivity.com.atlassian.confluence.user=false
#log4j.logger.bucket.user=DEBUG,console
#log4j.additivity.bucket.user=false

To this:

###
# Atlassian User
###
log4j.logger.com.atlassian.user=DEBUG, confluencelog
log4j.additivity.com.atlassian.user=false
log4j.logger.com.atlassian.confluence.user=DEBUG,confluencelog
log4j.additivity.com.atlassian.confluence.user=false
log4j.logger.bucket.user=DEBUG,confluencelog
log4j.additivity.bucket.user=false
log4j.logger.com.atlassian.seraph=DEBUG, confluencelog
log4j.additivity.com.atlassian.seraph=false
log4j.logger.com.opensymphony.user=DEBUG, confluencelog
log4j.additivity.com.opensymphony.user=false
  • 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.

    If you are using LDAP, run the External User Test tool and attach a copy of the output to the support ticket.