To configure a domain with LDAP authentication, perform the following steps:
Step 1 Click Add Domain or the Configure icon for the domain to edit. The Add Domain or Edit Domain window is displayed.
Step 2 If adding the domain, select LDAP from the Authentication Type menu. The LDAP domain configuration fields are displayed.
Step 3 If adding the domain, enter a descriptive name for the authentication domain in the Domain Name field. This is the domain name users will select in order to log into the SonicWALL SRA appliance user portal. It can be the same value as the Server Address field.
Step 4 Enter the IP address or domain name of the server in the Server Address field.
Step 5 Enter the search base for LDAP queries in the LDAP baseDN field. An example of a search base string is CN=Users,DC=yourdomain,DC=com.
Tip It is possible for multiple OUs to be configured for a single domain by entering each OU on a separate line in the LDAP baseDN field. In addition, any sub-OUs will be automatically included when parents are added to this field.
Step 6 Enter the common name of a user that has been delegated control of the container that user will be in along with the corresponding password in the Login Username and Login Password
fields.
Note When entering Login Username and Login Password, remember that the SRA appliance binds to the LDAP tree with these credentials and users can log in with their
sAMAccountName.
Step 7 Enter the name of the layout in the Portal Name field. Additional layouts may be defined in the
Portals > Portals page.
Step 8 Optionally select the Allow password changes (if allowed by LDAP server) checkbox. This option, if allowed by your LDAP server, will enable users to change their LDAP password during an SSL VPN session.
Step 9 Optionally select the Use SSL/TLS checkbox. This option allows for the SSL/TLS encryption to be used for LDAP password exchanges. This option is disabled by default as not all LDAP servers are configured for SSL/TLS.
Step 10 Optionally select the Enable client certificate enforcement checkbox to require the use of client certificates for login. By checking this box, you require the client to present a client certificate for strong mutual authentication. Two additional fields will appear:
• Verify user name matches Common Name (CN) of client certificate - Select this checkbox to require that the user’s account name match their client certificate.
• Verify partial DN in subject - Use the following variables to configure a partial DN that will match the client certificate:
– User name: %USERNAME%
– Domain name: %USERDOMAIN%
– Active Directory user name: %ADUSERNAME%
– Wildcard: %WILDCARD%
Step 11 Select the Auto-assign groups at login check box to assign users to a group when they log in. Users logging into LDAP domains are automatically assigned in real time to SSL VPN groups based on their external LDAP attributes. If a user’s external group membership has changed, their SSL VPN group membership automatically changes to match the external group
membership.
Step 12 Optionally select the One-time passwords checkbox to enable the One Time Password feature. A drop-down list will appear, in which you can select if configured, required for all users, or using domain name. These are defined as:
• if configured - Only users who have a One Time Password email address configured will use the One Time Password feature.
• required for all users - All users must use the One Time Password feature. Users who do not have a One Time Password email address configured will not be allowed to login.
• using domain name - Users in the domain will use the One Time Password feature. One Time Password emails for all users in the domain will be sent to [email protected]. If you selected if configured or required for all users in the One-time passwords drop-down list, the LDAP e-mail attribute drop-down list will appear, in which you can select mail,
userPrincipalName, or custom. These are defined as:
• mail - If your LDAP server is configured to store email addresses using the “mail” attribute, select mail.
• mobile or pager - If your AD server is configured to store mobile or pager numbers using either of these attributes, select mobile or pager, respectively. Raw numbers cannot be
• userPrincipalName - If your LDAP server is configured to store email addresses using the “userPrincipalName” attribute, select userPrincipalName.
• custom - If your LDAP server is configured to store email addresses using a custom attribute, select custom. If the specified attribute cannot be found for a user, the email address assigned in the individual user policy settings will be used. If you select custom, the Custom attribute field will appear. Type the custom attribute that your LDAP server uses to store email addresses. If the specified attribute cannot be found for a user, the email address will be taken from their individual policy settings.
If using domain name is selected in the One-time passwords drop-down list, the E-mail domain field will appear instead of the LDAP e-mail attribute drop-down list. Type in the domain name where one-time password emails will be sent (for example, abc.com).
Step 13 Select the type of user from the User Type drop-down list. All users logging in through this domain will be treated as this user type. The choices depend on user types defined already. Some possible choices are:
• External User – Users logging into this domain are treated as normal users without administrative privileges.
• External Administrator – Users logging into this domain are treated as administrators, with local SSL VPN admin credentials. These users are presented with the admin login page.
This option allows the SSL VPN administrator to configure a domain that allows SSL VPN admin privileges to all users logging into that domain.
SonicWALL recommends adding filters that allow administrative access only to those users who are in the correct group. You can do so by editing the domain on the Users > Local Groups page.
• Read-only Administrator – Users logging into this domain are treated as read-only administrators and can view all information and settings, but cannot apply any changes to the configuration. These users are presented with the admin login page.
Step 14 Click Accept to update the configuration. Once the domain has been added, the domain will be added to the table on the Portals > Domains page.