Then you need to choose what could you use as a nameid. I would suggest to remove all custom additions to the template file for now, and also remove any configurations you could add using "SAML -> Configure Custom NameId" page too. Overall, have you followed all steps in this doc, including modifying the template file and adding custom attribute to serve as email nameid? Is it something configurable at O365 side? I see that our doc was suggesting to release nameid of "emailAddress" type.
`It explicitly requests nameid of "urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" type, and this request will take priority over whatever is specified in its metadata, AFAICR.
GlobalProtect Gateway: In the Global Protect client, enter into Portal field, then click Connect.This is SAML request your O365 instance sends: GlobalProtect Portal: Go to /global-protect/portal/portal.esp
This will be configured in the app UI see Group attribute instructions (step 8) above. The following SAML attribute is supported: Select the appropriate filter from the groups dropdown menu and type the preferred value into the field. To send groups as a part of SAML assertion, in Okta select the Sign On tab for the Palo Alto Networks app, then click Edit: Navigate to Network > GlobalProtect > Gateways. Select the Authentication Profile you configured in step 5. Navigate to Authentication, then click Add. Navigate to Network > GlobalProtect > Portals. Refer to the following Palo Alto Networks documentation for configuring a GlobalProtect Gateway: Refer to the following Palo Alto Networks documentation for configuring a GlobalProtect Portal:
Once you have set up the Okta as IDP you need to create either a new Portal or a new Gateway or both for the GlobalProtect components. Select the Advanced tab in the Authentication Profile, then chose the Allow List. IdP Server Profile: Select an IdP Server Profile created in step 4 as the IdP Server Profile from the dropdown.Ĭertificate for Signing Requests: Select None.Įnable Single Logout (optional): Check this option in order to enable SLO. Type: Select SAML from the dropdown menu. Name: Provide a name for the Authentication profile. Navigate to Device > Authentication Profile, click Add, then enter the following: Make sure the options Validate Identity Provider Certificate and Validate Metadata Signature are unchecked. Sign into the Okta Admin dashboard to generate this value. Then click Browse to locate and upload it to Palo Alto Networks GlobalProtect:
#GLOBALPROTECT SAML DOWNLOAD#
Identity Provider Metadata: Download and save the following. Profile Name: Enter a preferred profile name. Navigate to Device > Server Profiles > SAML Identity Provider. Now that you have completed the set up in Okta, login to your Palo Alto Networks application as an administrator and follow the steps below to configure Okta as your IDP. Note: If global protect is configured on port 443, then the admin UI moves to port 4443. In Okta, select the General tab for the Palo Alto Networks - GlobalProtect app, then click Edit:Įnter into the Base URL field. The Okta/Palo Alto Networks - GlobalProtect SAML integration currently supports the following features:įor more information on the listed features, visit the Okta Glossary.
#GLOBALPROTECT SAML HOW TO#
For reference, here is documentation describing How to create a CA-signed certificate for Palo Alto Networks SAML Applications.