User Identification : Device > User Identification > Group Mapping Settings

Device > User Identification > Group Mapping Settings
•
Device > User Identification > Group Mapping Settings
To base security policies and reports on users and user groups, the firewall retrieves the list of groups and the corresponding list of members specified and maintained on your directory servers. The firewall supports a variety of LDAP directory servers, including the Microsoft Active Directory (AD), the Novell eDirectory, and the Sun ONE Directory Server.
The number of distinct user groups that each firewall or Panorama can reference across all policies varies by model. Regardless of model, though, you must configure an LDAP server profile (Device > Server Profiles > LDAP) before you can create a group mapping configuration.
Note: 
*
The complete procedure for mapping usernames to groups requires additional tasks besides creating group mapping configurations.
Add and configure the following fields as needed to create a group mapping configuration. To remove a group mapping configuration, select and Delete it. If you want to disable a group mapping configuration without deleting it, edit the configuration and clear the Enabled option.
Note:
If you create multiple group mapping configurations that use the same base distinguished name (DN) or LDAP server, the group mapping configurations cannot contain overlapping groups (for example, the Include list for one group mapping configuration cannot contain a group that is also in a different group mapping configuration).
Device > User Identification > Group Mapping Settings
Device > User Identification > Group Mapping Settings > Server Profile
By default, User Domain is blank: the firewall automatically detects the domain names for Active Directory servers. If you enter a value, it overrides any domain names that the firewall retrieves from the LDAP source. Your entry must be the NetBIOS name.
Note: 
•
Search Filter—Enter an LDAP query that specifies which groups to retrieve and track.
•
Object Class—Enter a group definition. The default is objectClass=group, which specifies that the system retrieves all objects in the directory that match the group Search Filter and have objectClass=group.
•
Search Filter—Enter an LDAP query that specifies which users to retrieve and track.
•
Object Class—Enter a user object definition. For example, in Active Directory, the objectClass is user.
•
Primary Username—Specify the attribute the User-ID source provides for the username (for example, userPrincipalName or sAMAccountName)
Note: 
•
E-Mail—Specify the attribute the User-ID source provides for the email address. The default is mail.
•
Alternate Username 1-3—Specify up to three additional attributes that correspond with the formats your User-ID sources can send.
•
Group Name—Specify the attribute the User-ID source uses for the group name attribute. The default for Active Directory is name and the default for Novell eDirectory or Sun ONE Directory Server is cn.
•
Group Member—Specify the attribute the User-ID source uses for the group member. The default is member.
•
E-Mail—Specify the attribute the User-ID source uses for the email address. The default is mail.
Device > User Identification > Group Mapping Settings > Group Include List
Fastpath: 
Device > User Identification > Group Mapping Settings > Custom Group
•
Name—Enter a custom group name that is unique in the group mapping configuration for the current firewall or virtual system.
•
LDAP Filter—Enter a filter of up to 2,048 characters.
Fastpath: 
The combined maximum for the Included Groups and Custom Group lists is 640 entries.
To delete a custom group, select and Delete it. To make a copy of a custom group, select and Clone it and then edit the fields as appropriate.
CAUTION: 
After adding or cloning a custom group, you must Commit your changes before your new custom group is available in policies and objects.
User Identification