The Seapine License Server supports the Lightweight Directory Access Protocol (LDAP), which allows you to define users once and share them across multiple computers and applications. Before you set any LDAP options you must already have an LDAP server or Active Directory server configured.

If your company already uses an LDAP server configuring the Seapine License Server to use LDAP will make user administration easier. User information, such as phone numbers and email addresses, is stored on the LDAP server and accessed by the license server. This ensures the Seapine License Server is always in sync with your company’s user directory.

Adding LDAP servers

1. Start the Seapine License Server Admin Utility.
2. Click Server Options or choose View > Server Options.
3. Click the LDAP tab and then click Add.
4. Enter a descriptive Name to identify the LDAP server.
5. Enter the LDAP server Host address. This is the IP address or alias of the LDAP server. For example, ldap.wysicorp.com.
6. Enter the LDAP server Port number. This is the port where the LDAP server resides. The default port is 389.
7. Enter the Base directory DN. This field specifies where to start searching from in the LDAP tree. Leave this field empty to use the root DN.
   
   For example, your Base DN is wysicorp.com and includes development, sales, marketing, and support nodes. Entering o=sales, dc=wysicorp, dc=com tells the license server to start searching from the sales node.
8. Optionally enter the Host address and Port number of a backup server.
   
   The backup server is only queried if the primary server cannot be reached.
9. Select Use anonymous binding for query to anonymously access the LDAP server.
   
   You must be an authenticated, non-anonymous user if you want to perform LDAP operations such as password checking.
10. Enter a Username, User DN, and Password if anonymous binding is not enabled.
    
    Username is the name of the user you want to connect to the LDAP server as. The license server will try to automatically connect to the LDAP server using one of the supported SASL authentication mechanisms. Leave the username field empty to force simple authentication with the LDAP server.
    
    User DN is the distinguished name (DN) of the user. This sequence of attributes and values specifies the location of an entry in the LDAP tree. For example: cn=Administrator, cn=users, dc=addoej, dc=wyiscorp,dc=com.
    
    Password is the password of the user you want to connect to the LDAP server as.
11. Select This is an Active Directory server if the server is a Microsoft Active Directory server.
12. Enter any Custom Attributes.
    
    Username specifies the username attribute in the server’s schema. The attribute is set to UID by default, which is the currently proposed as a standard in RFC 1274. If you are accessing an Active Directory server this field defaults to sAMAccountName.
    
    Email specifies the email address attribute in the server’s schema. The attribute is set to mail by default, which is proposed as a standard in RFC 1274.
13. Click Test LDAP Connection to test the LDAP server parameters. If the connection is not successful correct any mistakes and re-test it.
14. Click OK to save the settings and add the server.