authentik/website/integrations/networking/globalprotect/index.md at e7fcfb7e67d5df3e8a8a5da170f18fa4c6b98731

mirror of https://github.com/goauthentik/authentik synced 2026-04-27 18:07:15 +02:00

Files

Teffen Ellis 6ed5cb5249 website/docs: Modal and wizard button labels (#21549 )

* website/integrations: rename "Create with Provider" to "New Application"

The application list page now uses a split-button labeled
"New Application" instead of the old "Create with Provider" dropdown.
Update all 113 integration guides to match.

* website/docs: update flow, stage, and policy button labels

- "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons
- "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit
- "Create and bind stage" → "New Stage" / "Bind Existing Stage"
- "Create" (binding submit) → "Create Stage Binding"

* website/docs: update provider button labels

- "Create" → "New Provider" for trigger buttons
- "Create with Provider" → "New Application" in RAC docs
- "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt"
  for related entity creation

* website/docs: update directory button labels

- "Create" → "New Source" for federation/social login pages
- "Create" → "New Role", submit → "Create Role"
- "Create" → "New Invitation"
- Policy binding submit → "Create Policy Binding"

* website/docs: update endpoint device and system management button labels

- "Create" → "New Endpoint Connector", "New Enrollment Token",
  "New Device Access Group", "New Flow"
- Submit → "Create Device Access Group"
- "Create" → "New Notification Rule", "New Notification Transport"
- Binding submit → "Create Policy Binding"

* Reorganize policy documentation

* website/docs: address policy docs review feedback

* post-rebase

* website/docs: Reorganize policy documentation -- Revisions (#21601)

* apply suggestions

* Fix escaped.

* Fix whitespace.

* Update button label.

* Fix phrasing.

* Fix phrasing.

* Clean up stragglers.

* Format.

---------

Co-authored-by: Dominic R <dominic@sdko.org>

2026-04-16 17:35:38 +00:00

3.9 KiB

Raw Blame History

title, sidebar_label, support_level

title	sidebar_label	support_level
Integrate with GlobalProtect	GlobalProtect	community

What is GlobalProtect

GlobalProtect enables you to use Palo Alto Networks next-gen firewalls or Prisma Access to secure your mobile workforce.

Palo Alto Networks GlobalProtect platform is a paid enterprise product.

-- https://docs.paloaltonetworks.com/globalprotect

Preparation

The following placeholders are used in this guide:

gp.company is the FQDN of the GlobalProtect portal.
authentik.company is the FQDN of the authentik installation.

:::info This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application. :::

:::caution A trusted web certificate is required to be bound to the GlobalProtect Portal. This can be signed by a trusted internal Root Certificate Authority (CA); however, a self-signed certificate, a certificate outside of its validity, or a non-standard confirming certificate (such as a lifespan not trusted by modern browsers) will error out on SAML authentication. :::

authentik Configuration

To support the integration of GlobalProtect with authentik, you need to create an application/provider pair in authentik.

Create an Application and Provider in authentik

Log in to authentik as an administrator and open the authentik Admin interface.
Navigate to Applications > Applications and click New Application to open the application wizard.
- Application: Provide a descriptive name, an optional group, and UI settings. Take note of the slug as it will be required later.
- Choose a Provider type: Select SAML Provider.
- Configure the Provider:
  - Set the ACS URL to https://gp.company:443/SAML20/SP/ACS. (Note the absence of the trailing slash and the inclusion of the web interface port)
  - Set the Issuer to https://authentik.company/application/saml/<application_slug>/sso/binding/redirect/.
  - Set the Service Provider Binding to Post.
  - Under Advanced protocol settings, select an available Signing certificate.
Click Submit to save the new application and provider.

Download the metadata

Log in to authentik as an administrator and open the authentik Admin interface.
Navigate to Applications > Providers > Provider Name and download the SAML metadata.

GlobalProtect configuration

Navigate to the GlobalProtect configuration device (Firewall or Panorama).
Navigate to 'SAML Identity Provider' on the Device tab and choose the 'import' option.

Provide a name for the profile.
Import the metadata file downloaded earlier. (This will automatically install the authentik signing certificate to the system upon commit.)
Select 'Validate Identity Provider Certificate' if desired.

Navigate to 'Authentication Profile' on the Device tab and add a new profile.

Type: SAML
IdP Server Profile: The profile just created
Certificate for Signing Requests: None (Optionally configure authentik for mutual SAML signature)
Certificate Profile: None (Optionally configure profile to validate the authentik signing cert)
Username Attribute: username

Choose 'Advanced' within the profile and add 'all'. This will have only authentik control the authorization.
Navigate to the 'GlobalProtect Portal Configuration' and choose the portal for SAML access.

Under 'Authentication' select the 'Authentication Profile' to the one just created. Leave all other settings as default.
Optionally choose to require client access via separately issued client cert as well. If not using a client cert, select 'Yes (User Credentials OR Client Certificate Required)'.

Make the same exact changes to the 'GlobalProtect Gateway Configuration'.
Commit the changes to the firewall.

3.9 KiB Raw Blame History