Connection Settings

First, start by connection settings which will tell eXo how to connect to your directory server. These settings are very close to the JNDI API context parameters. This configuration is activated by the init-param ldap.config of service LDAPServiceImpl.




<component>

  <key>org.exoplatform.services.ldap.LDAPService</key>

  <type>org.exoplatform.services.ldap.impl.LDAPServiceImpl</type>

  <init-params>

    <object-param>

      <name>ldap.config</name>

      <description>Default ldap config</description>

      <object type="org.exoplatform.services.ldap.impl.LDAPConnectionConfig">

        <field name="providerURL">

          <string>ldap://127.0.0.1:389,10.0.0.1:389</string>

        </field>

        <field name="rootdn">

          <string>CN=Manager,DC=exoplatform,DC=org</string>

        </field>

        <field name="password">

          <string>secret</string>

        </field>

        <!-- field name="authenticationType"><string>simple</string></field -->

        <field name="version">

          <string>3</string>

        </field>

        <field name="referralMode">

          <string>follow</string>

        </field>

        <!-- field name="serverName"><string>active.directory</string></field -->

      </object>

    </object-param>

  </init-params>

</component>

providerURL: LDAP server URL (see PROVIDER URL). For multiple LDAP servers, use comma separated list of host:port (For example, ldap://127.0.0.1:389,10.0.0.1:389).
rootdn: distinguished name of user that will be used by the service to authenticate on the server (see SECURITY PRINCIPAL).
password: password for user rootdn (see SECURITY CREDENTIALS).
authenticationType: type of authentication to be used (see SECURITY AUTHENTICATION). Use one of none, simple, strong. Default is simple.
version: LDAP protocol version (see java.naming.ldap.version). Set to 3 if your server supports LDAP V3.
referralMode: one of follow, ignore, throw (see REFERRAL).
serverName: you will need to set this to active.directory to work with Active Directory servers. Any other value will be ignored and the service will act as on a standard LDAP.