Customization → User Synchronization → User Authentication Providers → Configuring Microsoft Active Directory authentication

Configuring Microsoft Active Directory authentication

Each user account set up uses an authentication provider to facilitate user logon. By default, a pre-defined Application authentication provider is included. Multiple authentication types are supported, including those using the Lightweight Directory Access (LDAP) protocol. You can use the Manage Providers dialog box to add, modify or remove an authentication provider that uses Microsoft Active Directory.

To configure Microsoft Active Directory authentication

  1. In the desktop System Settings module, under Actions, click Manage Providers.
  2. In the Manage Providers dialog box, click Add.
  3. In the Authentication Provider Name box, type a name.
  4. In the Authentication Type list, select Active Directory.
  5. In the Server box, type the fully qualified distinguished name (FqDN) of the Microsoft Active Directory server, for example ad.serena.com.
  6. In the Domain/Filter box, type the Lightweight Directory Access (LDAP) query format for the provider, for example (objectclass=user).
  7. Type values for the corresponding boxes (first name, last name, email, and user name). The default values should be correct in most cases for Microsoft Active Directory.
  8. In the Distinguished Name box, the field can accept a username (such as username) or a qualified domain name (such as domain\username) in addition to a full Lightweight Directory Access (LDAP) distinguished name.
  9. Under Connect As, enter a user name and password. This is used to verify that the provider settings have been entered correctly. In Microsoft Active Directory, the user name can be a simple user name, a qualified domain name, or a full distinguished name.
  10. Click Apply. This will verify that Microsoft Active Directory is accessible in the path specified, and that the query returns more than zero users. There is no user validation, as this would require using actual user passwords.
  11. If you receive a "Server does not exist" error, modify the provider properties and try again. If no errors return, close the Manage Providers dialog.

Copyright © 2003–2009 Serena Software, Inc. All rights reserved.