Until we finish defining the upcoming atlassianuser.xml configuration, Atlassian User will have to be configured for Confluence by directly editing a Spring configuration file (unless you are using osuser.xml).

Find here an example atlassianUserContext.xml file, which can be taken and edited slightly to achieve the configurations you want.

Configuration

File

Instructions

Hibernate plus LDAP (cached)

DEV:atlassianUserContext.xml

Download this file and search for the 'ldapRepository' bean, then follow these instructions. To upgrade from OSUser, read this document.
  • No labels

2 Comments

  1. Stefan Farthofer

    Jan 12, 2006

    I have deployed this configuration file on Confluence 2.1.1 and the integration with our ActiveDirectory seems to work fine apart from two things:

    • As long as any text is provided as password, the authentication for LDAP users always succeeds, no matter if the password does match the LDAP password. This actually helps since I use a custom login URL which NTLM authenticates users and sets the Seraph cookie. Just wanted to know if this was the intended behaviour.
    • We have some pages which heavily use the children and include macros. I have noticed very long loading times for these pages and decided to have a closer look. It turns out that in the course of loading such a page confluence does issue a lot of queries to the LDAP server, many of which are duplicates of previous queries.

    Could I have made some mistakes with the configuration file? I only changed the LDAP server, some of the attribute mappings and the user and group query filter. I also found CONF-4917 which may be related to the performance issues I experience.

    1. Tom Davies

      Jan 13, 2006

      Please open a support case at http://support.atlassian.com

      Thanks,
      Tom

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.