Skip to main content

Auth Setting

Auth settings configure authentication methods for GlobalProtect mobile agent connections in Strata Cloud Manager. The scm CLI provides commands to create, update, delete, and load auth settings.

Overview

The auth-setting commands allow you to:

  • Create auth settings with SAML, client certificate, or LDAP authentication
  • Update existing auth setting configurations
  • Delete auth settings that are no longer needed
  • Bulk import auth settings from YAML files
  • Export auth settings for backup or migration

Authentication Types

Auth settings support the following authentication methods:

TypeDescription
samlSAML-based single sign-on via an identity provider
client-certificateCertificate-based authentication
ldapLDAP directory-based authentication

Set Auth Setting

Create or update an auth setting.

Syntax

scm set mobile-agent auth-setting NAME [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEName of the auth settingYes

Options

OptionDescriptionRequired
--folder TEXTFolder locationYes
--description TEXTDescriptionNo
--auth-type TEXTAuthentication type (saml, client-certificate, ldap)No
--os TEXTOperating system (Any, Windows, macOS, Linux, iOS, Android, ChromeOS)No
--max-user INTMaximum number of concurrent usersNo
--saml-idp TEXTSAML identity provider profile nameNo
--certificate-profile TEXTCertificate profile nameNo
--ldap-profile TEXTLDAP server profile nameNo

Examples

Create SAML Auth Setting

$ scm set mobile-agent auth-setting "saml-auth" \
--folder "Mobile Users" \
--auth-type saml \
--saml-idp "okta-idp" \
--os Any
---> 100%
Created auth setting: saml-auth in folder Mobile Users

Create LDAP Auth Setting

$ scm set mobile-agent auth-setting "ldap-auth" \
--folder "Mobile Users" \
--auth-type ldap \
--ldap-profile "corp-ldap" \
--os Windows \
--max-user 500
---> 100%
Created auth setting: ldap-auth in folder Mobile Users

Create Certificate Auth Setting

$ scm set mobile-agent auth-setting "cert-auth" \
--folder "Mobile Users" \
--auth-type client-certificate \
--certificate-profile "gp-cert-profile" \
--os macOS
---> 100%
Created auth setting: cert-auth in folder Mobile Users

Delete Auth Setting

Delete an auth setting from SCM.

Syntax

scm delete mobile-agent auth-setting NAME [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEName of the auth setting to deleteYes

Options

OptionDescriptionRequired
--folder TEXTFolder locationYes
--forceSkip confirmation promptNo

Example

$ scm delete mobile-agent auth-setting "saml-auth" \
--folder "Mobile Users" \
--force
---> 100%
Deleted auth setting: saml-auth from folder Mobile Users

Load Auth Setting

Load multiple auth settings from a YAML file.

Syntax

scm load mobile-agent auth-setting [OPTIONS]

Options

OptionDescriptionRequired
--file TEXTPath to the YAML fileYes
--folder TEXTOverride folder location for all objectsNo
--snippet TEXTOverride snippet location for all objectsNo
--device TEXTOverride device location for all objectsNo
--dry-runSimulate execution without applying changesNo

YAML File Format

---
auth_settings:
- name: saml-auth
folder: "Mobile Users"
auth_type: saml
saml_idp: "okta-idp"
os: Any

- name: ldap-auth
folder: "Mobile Users"
auth_type: ldap
ldap_profile: "corp-ldap"
os: Windows
max_user: 500

Examples

Load with Original Locations

$ scm load mobile-agent auth-setting --file auth_settings.yml
---> 100%
✓ Loaded auth setting: saml-auth
✓ Loaded auth setting: ldap-auth

Successfully loaded 2 out of 2 auth settings from 'auth_settings.yml'

Load with Folder Override

$ scm load mobile-agent auth-setting \
--file auth_settings.yml \
--folder "Mobile Users"
---> 100%
✓ Loaded auth setting: saml-auth
✓ Loaded auth setting: ldap-auth

Successfully loaded 2 out of 2 auth settings from 'auth_settings.yml'
note

When using container override options (--folder, --snippet, --device), all auth settings will be loaded into the specified container, ignoring the container specified in the YAML file.

Show Auth Setting

Display auth setting objects.

Syntax

scm show mobile-agent auth-setting [NAME] [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEName of a specific auth setting; omit to list allNo

Options

OptionDescriptionRequired
--folder TEXTFolder locationYes
--output, -o [table|json|yaml]Output format (default: table)No
--max-results INTEGERMaximum number of results to displayNo
note

When no NAME is specified, all items are listed by default.

Examples

Show Specific Auth Setting

$ scm show mobile-agent auth-setting "saml-auth" \
--folder "Mobile Users"
---> 100%
Auth Setting: saml-auth
Location: Folder 'Mobile Users'
Auth Type: saml
OS: Any
SAML IDP: okta-idp

List All Auth Settings (Default Behavior)

$ scm show mobile-agent auth-setting --folder "Mobile Users"
---> 100%
Auth Settings in folder 'Mobile Users':
------------------------------------------------------------
Name: saml-auth
Auth Type: saml
OS: Any
------------------------------------------------------------
Name: ldap-auth
Auth Type: ldap
OS: Windows
------------------------------------------------------------

Backup Auth Settings

Backup all auth settings from a specified location to a YAML file.

Syntax

scm backup mobile-agent auth-setting [OPTIONS]

Options

OptionDescriptionRequired
--folder TEXTFolder locationNo*
--snippet TEXTSnippet locationNo*
--device TEXTDevice locationNo*
--file TEXTOutput file pathNo

* One of --folder, --snippet, or --device is required.

Examples

Backup from Folder

$ scm backup mobile-agent auth-setting --folder "Mobile Users"
---> 100%
Successfully backed up 5 auth settings to auth-setting-mobile-users.yaml

Backup with Custom Filename

$ scm backup mobile-agent auth-setting \
--folder "Mobile Users" \
--file mobile-auth-backup.yaml
---> 100%
Successfully backed up 5 auth settings to mobile-auth-backup.yaml

Best Practices

  1. Use Descriptive Names: Name auth settings to reflect their authentication method and purpose, such as saml-okta-prod or ldap-corp-windows.
  2. Limit by OS When Possible: Restrict auth settings to specific operating systems to enforce platform-appropriate authentication methods.
  3. Set Max User Limits: Configure --max-user to prevent resource exhaustion from excessive concurrent connections.
  4. Backup Before Changes: Always backup existing auth settings before making bulk modifications via load commands.
  5. Use Dry Run for Validation: Test YAML configurations with --dry-run before applying changes to production environments.