Map Users to Groups
Add an LDAP server profile.
The profile defines how the firewall connects to the directory servers from which it collects group mapping information. You can add up to four servers to the profile but they must be the same
Configure an LDAP Server Profile:
Device > Server Profiles > LDAP, click
Add, and enter a
For each LDAP server, click
and enter the server
Name, IP address (
LDAP Server), and
(default is 389).
Based on your
selection (for example,
active-directory), the firewall automatically populates the correct LDAP attributes in the group mapping settings. However, if you customized your LDAP schema, you might need to modify the default settings.
field, enter the Distinguished Name (DN) of the LDAP tree location where you want the firewall to begin its search for user and group information.
Enter the authentication credentials for binding to the LDAP tree in the
can be a fully qualified LDAP name (for example,
) or a user principal name (for example,
to save the profile.
Configure the server settings in a group mapping configuration.
Device > User Identification > Group Mapping Settings.
Select a virtual system (
Location) if the firewall has multiple.
and enter a unique
to identify the group mapping configuration.
Select the LDAP
you just created.
) By default, the
field is blank: the firewall automatically detects the domain names for Active Directory (AD) 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 domain name.
) To filter the groups that the firewall tracks for group mapping, in the Group Objects section, enter a
Group Name, and
) To filter the users that the firewall tracks for group mapping, in the User Objects section, enter a
(user definition), and
) To match User-ID information with email header information identified in the links and attachments of emails forwarded to WildFire™, enter the list of email domains in your organization in the Mail Domains section,
field. Use commas to separate multiple domains (up to 256 characters). After you click
OK, PAN-OS automatically populates the
field based on your LDAP server type (Sun/RFC, Active Directory, or Novell). When a match occurs, the username in the WildFire log email header section will contain a link that opens the
tab, filtered by user or user group.
Make sure the
check box is selected.
Limit which groups will be available in policy rules.
Required only if you want to limit policy rules to specific groups. By default, if you don’t specify groups, all groups are available in policy rules.
Any custom groups you create will also be available in the Allow List of authentication profiles.
Add existing groups from the directory service:
Group Include List
In the Available Groups list, select the groups you want to appear in policy rules and click the Add icon.
If you want to base policy rules on user attributes that don’t match existing user groups, create custom groups based on LDAP filters:
tab and click
Enter a group
that is unique in the group mapping configuration for the current firewall or virtual system. If the
has the same value as the Distinguished Name (DN) of an existing AD group domain, the firewall uses the custom group in all references to that name (for example, in policies and logs).
of up to 2,048 UTF-8 characters and click
OK. The firewall doesn’t validate LDAP filters, so it’s up to you to ensure they are accurate.
To minimize the performance impact on the LDAP directory server, use only indexed attributes in the filter.
to save your changes.
Commit your changes.
Commit. A commit is necessary before you can use custom groups in policies and objects.
After configuring the firewall to retrieve group mapping information from an LDAP server, but before configuring policies based on the groups it retrieves, you must either wait for the firewall to refresh its group mappings cache or refresh the cache manually. To verify which groups you can currently use in policies,
access the firewall CLI
and run the
show user group
command. To determine when the firewall will next refresh the group mappings cache, run the
show user group-mapping statistics
command and check the
. To manually refresh the cache, run the
debug user-id refresh group-mapping all