Panorama authorization/restriction for administrator access using SAML 2.0 and Access Domain (AD) enforcement
Objective
In an environment like Security Managed services, you'll leverage a single Panorama to manage multiple customers' firewalls. This article will answer the challenge of providing each customer access to the Device Groups and Templates that they own and should hide other customer resources.
You will be configuring SAML2.0, and in this article, we'll be using Okta as an example which will control the Access Domain that users can access. For more info about Access Domain, click here .
As for the Panorama part, you'll need to configure the Access Domains that map to their respective Device Groups and Templates.
Environment
- Panorama 9.1.x and above
- SAML2.0
Procedure
Panorama Configuration
1. Configure the Access Domain with its Device Group and Template from Panorama > Access Domain, and the result is as below.
2. Verify that the Panorama admin role for saml-ar is as below; go to Panorama > Admin Roles
3. Configure the Authentication Profile, setting the proper attribute names according to the IdP side, Panorama > Authentication Profiles
4. Configure the Administrators to authenticate against the SAML authentication profile, Panorama > Setup > Management tab > Authentication Settings
Okta Configuration
1. Ensure the Application Profile has configured the Admin Role and Access Domain as custom attributes; go to Directory > Profile Editor > [Click the profile corresponding to the configured Application]
2. Assign the user with the appropriate Admin Role and Access Domain; in our example, AD_1, AD_2, AD_3 will be accessible to the user; go to Directory > People > [click the username] > Palo Alto Network - Admin UI > click the pencil sign, which is the edit.
You will need to use a semi-colon as the separator for each Admin Role and Access Domain value,
and each Admin Role will have its corresponding Access Domain and vice-versa.
Result
1. Login to your Panorama using your SAML2.0 credential, and verify the Access Domains granted to you as shown below.
2. Sample output of authd.log
2026-10-28 05:33:14.217 -0700 debug: add_info_from_auth_profile_to_request(pan_auth_util.c:1104): MFA is not configured for the auth profile. No mfa server ids for the user "user2@cloud-raid.lab" (prof/vsys: saml/shared)
2026-10-28 05:33:14.217 -0700 debug: pan_auth_allowlist_response_process(pan_auth_state_engine.c:4256): added b_mfa = 0 with 0 factors for SAML authentication request
2026-10-28 05:33:14.217 -0700 debug: pan_auth_send_saml_resp(pan_auth_server.c:1884): pan_auth_mgr_add_admin_user_token() for SAML/CAS authed user user2@cloud-raid.lab
2026-10-28 05:33:14.217 -0700 debug: pan_auth_send_saml_resp(pan_auth_server.c:1897): Succeed to cache role/adomain saml-ar;saml-ar;saml-ar/AD_1;AD_2;AD_3 for user user2@cloud-raid.lab
2026-10-28 05:33:14.217 -0700 SAML SSO authenticated for user 'user2@cloud-raid.lab'. auth profile 'saml', vsys 'shared', server profile 'admin-ui.pantac.lab', IdP entityID 'http://www.okta.com/exkzm1hjydw3LkceY697', admin role 'saml-ar;saml-ar;saml-ar', access domain 'AD_1;AD_2;AD_3', From: 10.194.89.87.
2026-10-28 05:33:14.217 -0700 debug: _log_saml_respone(pan_auth_server.c:956): Sent PAN_AUTH_SUCCESS SAML response:(authd_id: 7683811876840409483) (return username 'user2@cloud-raid.lab') (auth profile 'saml') (NameID 'user2@cloud-raid.lab') (SessionIndex '_565c52e59d67ae78e5d5faf255f61571') (Single Logout enabled? 'No') (Is it CAS (cloud-auth-service)? 'No')
2026-10-28 05:33:14.285 -0700 debug: pan_auth_request_process(pan_auth_state_engine.c:3777): Receive request: msg type PAN_AUTH_REQ_GROUP, conv id 1198, body length 384
2026-10-28 05:33:14.285 -0700 debug: pan_db_funcs_request_process(pan_auth_state_engine.c:1759): init'ing group request (authorization)
2026-10-28 05:33:14.285 -0700 debug: pan_authd_handle_group_req(pan_auth_state_engine.c:1580): start to authorize admin user thru WebUI "user2@cloud-raid.lab" from "10.194.89.87"
2026-10-28 05:33:14.285 -0700 debug: pan_authd_handle_group_req(pan_auth_state_engine.c:1607): Authorization is verified for user user2@cloud-raid.lab
2026-10-28 05:33:14.285 -0700 debug: pan_auth_mgr_get_userinfo(pan_auth_mgr.c:2619): Found userinfo (name/role/ado) cache entry: user2@cloud-raid.lab/saml-ar;saml-ar;saml-ar/AD_1;AD_2;AD_3
2026-10-28 05:33:14.286 -0700 debug: pan_auth_cache_get_pw_profile_global(pan_auth_cache_pw_complexity.c:116): password complexity is NOT enabled, so change_expiry_period=0, change_warning_period=0, expired_adminlogin_count=0, expiry_grace_period=0 are ignored
2026-10-28 05:33:14.286 -0700 debug: pan_authd_handle_group_req(pan_auth_state_engine.c:1709): Sent PAN_GROUP_SUCCESS authorization response for user "user2@cloud-raid.lab": role/domain="saml-ar;saml-ar;saml-ar/AD_1;AD_2;AD_3"; expiring_in_days=-1; rem_grace_period=-1, rem_login_count=-1
Additional Information
Introduction to SAML
How to Configure SAML 2.0 for Palo Alto Networks - Admin UI