Map Roles and Permissions
Table of Contents
Expand all | Collapse all
-
-
- Add a Branch
- Add a Data Center
- Add a Branch Gateway
- Configure Circuits
- Configure Internet Circuit Underlay Link Aggregation
- Configure Private WAN Underlay Link Quality Aggregation
- Configure Circuit Categories
- Configure Device Initiated Connections for Circuits
- Add Public IP LAN Address to Enterprise Prefixes
- Manage Data Center Clusters
- Configure a Site Prefix
- Configure a DHCP Server
- Configure NTP for Prisma SD-WAN
- Configure the ION Device at a Branch Site
- Configure the ION Device at a Data Center
- Switch a Site to Control Mode
- Allow IP Addresses in Firewall Configuration
-
- Configure a Controller Port
- Configure Internet Ports
- Configure WAN/LAN Ports
- Configure a Loopback Interface
- Configure a PoE Port
- Configure and Monitor LLDP Activity and Status
- Configure a PPPoE Interface
- Configure a Layer 3 LAN Interface
- Configure Application Reachability Probes
- Configure a Secondary IP Address
- Configure a Static ARP
- Configure a DHCP Relay
- Configure IP Directed Broadcast
- VPN Keep-Alives
-
- Configure Prisma SD-WAN IPFIX
- Configure IPFIX Profiles and Templates
- Configure and Attach a Collector Context to a Device Interface in IPFIX
- Configure and Attach a Filter Context to a Device Interface in IPFIX
- Configure Global and Local IPFIX Prefixes
- Flow Information Elements
- Options Information Elements
- Configure the DNS Service on the Prisma SD-WAN Interface
- Configure SNMP
-
-
- Prisma SD-WAN Branch Routing
- Prisma SD-WAN Data Center Routing
-
- Configure Multicast
- Create a WAN Multicast Configuration Profile
- Assign WAN Multicast Configuration Profiles to Branch Sites
- Configure a Multicast Source at a Branch Site
- Configure Global Multicast Parameters
- Configure a Multicast Static Rendezvous Point (RP)
- Learn Rendezvous Points (RPs) Dynamically
- View LAN Statistics for Multicast
- View WAN Statistics for Multicast
- View IGMP Membership
- View the Multicast Route Table
- View Multicast Flow Statistics
- View Routing Statistics
- Prisma SD-WAN Incident Policies
-
- Prisma SD-WAN Branch HA Key Concepts
- Configure Branch HA
- Configure HA Groups
- Add ION Devices to HA Groups
- View Device Configuration of HA Groups
- Edit HA Groups and Group Membership
-
- Configure Branch HA with Gen-1 Platforms (2000, 3000, 7000, and 9000)
- Configure Branch HA with Gen-2 Platforms (3200, 5200, and 9200)
- Configure Branch HA with Gen-2 Embedded Switch Platforms (1200-S or 3200-L2)
- Configure Branch HA for Devices with Software Cellular Bypass (1200-S-C-5G)
- Configure Branch HA for Platforms without Bypass Pairs
- Configure Branch HA in a Hybrid Topology with Gen-1 (3000) and Gen-2 (3200) Platforms
- Prisma SD-WAN Incidents and Alerts
Map Roles and Permissions
Let us learn to map roles and permissions in Prisma SD-WAN.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
Mapping roles and permissions are a critical
part of the SAML enabled authorization process. Before you can access
the Prisma SD-WAN web interface as an authorized user, your role
must be mapped to a Palo Alto Networks role in the system. Through
role mapping as defined in the IdP system, user group memberships
are mapped to Palo Alto Networks authorized roles.
Your IdP administrator must include the following information
in the SAML response.
- Name ID—The Name ID of the end user. This attribute is required.
- Role—The end user role or group membership. This attribute is required.
- First Name or Last Name—The first name is required, the last name is optional.The format of the SAML response can be transient, persistent, email, or unspecified.
Ensure that the SAML assertions sent to Palo Alto
Networks contain either the cloudgenix_groups or memberOf attributes
that Palo Alto Networks uses to map users to Palo Alto Networks
roles. After a user is authenticated, assertions containing either cloudgenix_groups or memberOf is
automatically sent to Palo Alto Networks with various attributes
such as email ID, the first and last name of the end user. Palo
Alto Networks uses these assertions to map the end user to the corresponding
Palo Alto Networks role in the Palo Alto Networks system.
The
SAML response shows the assertions that include cloudgenix_groups ,
and memberOf attributes, and a custom role.
Sample SAML Response with cloudgenix_groups
</Attribute><Attribute Name="cloudgenix_groups"><AttributeValue>cloudgenix_tenant_network_admin</AttributeValue><AttributeValue>cloudgenix_tenant_viewonly</AttributeValue></Attribute>
Sample SAML Response with memberOf
<Attribute Name="memberOf" NameFormatt="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"><AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:-type="xs:anyType">cloudgenix_tenant_super</AttributeValue></Attribute>
Sample SAML Response with a Custom Role
<Attribute Name="memberOf" NameFormatt="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"><AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:-type="xs:anyType">admin</AttributeValue></Attribute>
After successful authentication, the end user is authorized to
access the Prisma SD-WAN web interface.
Map Roles for Identity Provider Administrators
Map your IdP roles to Palo Alto Networks roles using
the Active Directory Federation Services (ADFS) as an identity provider
(IdP). This process varies for each IdP. For example, an administrator
is mapped to a Palo Alto Networks role called cloudgenix_tenant_super and
another is mapped to a customer-specific role called network-admin.
The outgoing claim from the IdP must be in the following format:
- The User-Principal-Name should be mapped to Name ID. Palo Alto Networks requires this name to be the person’s email ID.
- The given name should be mapped to firstname and the surname to lastname.
- The Outgoing Claim Type should be CloudGenix_groups.
- The Outgoing Claim Value can be either a Palo Alto Networks role defined as cloudgenix_tenant_<role> or a customer specific role.
If the Outgoing Claim Value is a customer specific role, make
sure to map that role with a Palo Alto Networks role in the AAA
Configuration screen.