To configure the End Point Control profiles used by local groups
Lightweight Directory Access Protocol (LDAP) is a standard for querying and updating a directory. Because LDAP supports a multilevel hierarchy (for example, groups or organizational units), the SMA appliance can query this information and provide specific group policies or bookmarks based on LDAP attributes. By configuring LDAP attributes, the SMA appliance administrator can leverage the groups that have already been configured in an LDAP or Active Directory database, rather than needing to manually recreate the same groups in the SMA appliance.
After an LDAP authentication domain is created, a default LDAP group is created with the same name as the LDAP domain name. Although additional groups can be added or deleted from this domain, the default LDAP group cannot be deleted. If the user for which you created LDAP attributes enters the Virtual Office home page, the bookmark you created for the group the user is in displays in the Bookmarks Table.
For an LDAP group, you can define LDAP attributes. For example, you can specify that users in an LDAP group must be members of a certain group or organizational unit defined on the LDAP server. Or you can specify a unique LDAP distinguished name.
To add an LDAP attribute for a group so that a user has a bookmark assigned when entering the Virtual Office environment, complete the following steps
Select LDAP from the Authentication Type menu. The LDAP domain configuration fields are displayed.
CN=Users,DC=yourdomain,DC=com
.Optionally select Enable client certificate enforcement 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 appear:
Select Auto-assign groups at login to assign users to a group when they log in.
Users logging into Active Directory domains are automatically assigned in real time to Secure Mobile Access groups based on their external AD group memberships. If a user’s external group membership has changed, their Secure Mobile Access group membership automatically changes to match the external group membership.
Optionally, select One-time passwords to enable the One Time Password feature. A drop-down menu appears, in which you can select if configured, required for all users, or using domain name. These are defined as:
username@domain.com
.If you selected if configured or required for all users in the One-time passwords drop-down menu, the Active Directory AD e-mail attribute drop-down menu appears, in which you can select mail, mobile, pager, userPrincipalName, or custom. These are defined as:
If you select using domain name, an E-mail domain field appears following the drop-down menu. Type in the domain name where one-time password emails are sent (for example, abc.com).
Select the type of user from the User Type drop-down menu. All users logging in through this domain are treated as this user type. The choices depend on user types defined already. Some possible choices are:
External Administrator – Users logging into this domain are treated as administrators, with local Secure Mobile Access admin credentials. These users are presented with the admin login page.
This option allows the Secure Mobile Access administrator to configure a domain that allows Secure Mobile Access admin privileges to all users logging into that domain.
SonicWall Inc. 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.
On the General page, you can optionally fill out one or multiple LDAP Attribute fields with the appropriate names where name=value is the convention for adding a series of LDAP attributes. To see a full list of LDAP attributes, refer to the SonicWall Inc. LDAP Attribute document.
As a common example, fill out an attribute field with the memberOf= attribute which can bundle the following common variable types:
CN= - the common name. DN= - the distinguished name. DC= - the domain component.
You need to provide quote delimiters around the variables you bundle in the memberOf line. You separate the variables by commas. An example of the syntax using the CN and DC variables would be:
memberOf="CN=<string>, DC=<string>"
An example of a line you might enter into the LDAP Attribute field, using the CN and DC variables would be:
memberOf="CN=Terminal Server Computers,CN=Users,DC=sonicwall,DC=net"
Under Single Sign-On Settings, in the Automatically log into bookmarks list, select one of the following: