Configure Publisher to Use an LDAP Provider for Authentication Only

Configure Publisher to use an LDAP provider for authentication in conjunction with another security model for authorization.

  1. On the Administration page, under Security Center, click Security Configuration.
  2. Create a Local Superuser.

    Enter a Superuser Name and Password and select Enable Local Superuser check box. Enabling a local superuser ensures that you can access the Administration page of Publisher in case of security model configuration errors.

  3. Scroll down to the Authentication region. Select the Use LDAP check box.
  4. Enter the following:
    • URL

      For example: ldap://example.com:389/

      If you're using LDAP over SSL, then note the following:

      • the protocol is ldaps

      • the default port is 636

      An example URL would be: ldaps://example.com:636/

    • Administrator Username and Password for the LDAP server

      The Administrator user entered here must also be a member of the XMLP_ADMIN group.

    • Distinguished Name for Users

      For example: cn=Users,dc=example,dc=com

      The distinguished name values are case-sensitive and must match the settings in the LDAP server.

    • JNDI Context Factory Class

      The default value is com.sun.jndi.ldap.LdapCtxFactory

    • Attribute used for Login Username

      Enter the attribute that supplies the value for the Login user name. This is also known as the Relative Distinguished Name (RDN). This value defaults to cn.

    • Attribute used for user matching with authorization system - enter the attribute that supplies the value to match users to the authorization system. For example, orcleguid.

  5. Click Apply.
  6. Restart the Publisher server.