Set Up External Authentication
The following workflow describes how to set up the GlobalProtect portal and gateways to use an external authentication service. The supported authentication services are LDAP, Kerberos, RADIUS, or TACACS+.
This workflow also describes how to create an optional authentication profile that a portal or gateway can use to identify the external authentication service. This step is optional for external authentication because the authentication profile also can specify the local authentication database or None.
GlobalProtect also supports local authentication. To use local authentication, create a local user database (
) that contains the users and groups to which you want to allow VPN access and then refer to that database in the authentication profile.
Local User Database
- Create a server profile.The server profile identifies the external authentication service and instructs the firewall how to connect to that authentication service and access the authentication credentials for your users.If you are using LDAP to connect to Active Directory (AD), you must create a separate LDAP server profile for every AD domain.
- Selectand select the type of profile (DeviceServer ProfilesLDAP,Kerberos,RADIUS, orTACACS+).
- ClickAddand enter aNamefor the profile, such as GP-User-Auth.
- (LDAP only) Select theTypeof LDAP server.
- ClickAddin the Servers section and then enter the necessary information for connecting to the authentication server, including the serverName, IP address or FQDN of theServer, andPort.
- (RADIUS, TACACS+, and LDAP only) Specify settings to enable the authentication service to authenticate the firewall, as follows:
- RADIUS and TACACS+—Enter the sharedSecretwhen adding the server entry.
- LDAP—Enter theBind DNandPassword.
- (LDAP only) If you want the device to use SSL or TLS for a more secure connection with the directory server, select theRequire SSL/TLS secured connectioncheck box (selected by default). The protocol that the device uses depends on the serverPort:
- Any other port—The device first attempts to use TLS. If the directory server doesn’t support TLS, the device falls back to SSL.
- (LDAP only) For additional security, select theVerify Server Certificate for SSL sessionscheck box so that the device verifies the certificate that the directory server presents for SSL/TLS connections. To enable verification, you also have to select theRequire SSL/TLS secured connectioncheck box. For verification to succeed, the certificate must meet one of the following conditions:
- It is in the list of device certificates:. Import the certificate into the device, if necessary.DeviceCertificate ManagementCertificatesDevice Certificates
- The certificate signer is in the list of trusted certificate authorities:.DeviceCertificate ManagementCertificatesDefault Trusted Certificate Authorities
- ClickOKto save the server profile.
- (Optional) Create an authentication profile.The authentication profile specifies the server profile for the portal or gateways to use when they authenticate users. On a portal or gateway, you can assign one or more authentication profiles in one or more client authentication profiles. For descriptions of how an authentication profile within a client authentication profile supports granular user authentication, see Configure a GlobalProtect Gateway and Set Up Access to the GlobalProtect Portal.If users allow their passwords to expire, you may assign a temporary LDAP password to enable them to log in to the VPN. In this case, the temporary password may be used to authenticate to the portal, but the gateway login may fail because the same temporary password cannot be re-used. To prevent this, enable an authentication override in the portal configuration () to enable the agent to use a cookie to authenticate to the portal and use the temporary password to authenticate the gateway.NetworkGlobalProtectPortal
- SelectandDeviceAuthentication ProfileAdda new profile.
- Enter aNamefor the profile and then select the authenticationType:None,Local Database(the authentication database on the firewall),RADIUS,TACACS+,LDAP, orKerberos.
- If the authenticationTypeis RADIUS, TACACS+, LDAP, or Kerberos, select the authenticationServer Profilethat you created in 1 from the drop-down.
- Specify the domain name and username format. The device combines theUser DomainandUsername Modifiervalues to modify the domain/username string that a user enters during login. The device uses the modified string for authentication and uses theUser Domainvalue for User-ID group mapping. Modifying user input is useful when the authentication service requires domain/username strings in a particular format and you don’t want to rely on users to correctly enter the domain. You can select from the following options:
- To send only the unmodified user input, leave theUser Domainblank (the default) and set theUsername Modifierto the variable%USERINPUT%(the default).
- To prepend a domain to the user input, enter aUser Domainand set theUsername Modifierto%USERDOMAIN%\%USERINPUT%.
- To append a domain to the user input, enter aUser Domainand set theUsername Modifierto%USERINPUT%@%USERDOMAIN%.If theUsername Modifierincludes the%USERDOMAIN%variable, theUser Domainvalue replaces any domain string that the user enters. If theUser Domainis blank, that means the device removes any user-entered domain string.
- (Kerberos only) Configure Kerberos single sign-on (SSO) if your network supports it:
- Enter theKerberos Realm(up to 127 characters). This is the hostname portion of the user login name. For example, the user account name user@EXAMPLE.LOCAL has the realm EXAMPLE.LOCAL.
- Specify aKerberos Keytabfile: click theImportlink,Browseto the keytab file, and clickOK. During authentication, the endpoint first tries to use the keytab to establish SSO. If it succeeds, and the user attempting access is in theAllow List, authentication succeeds immediately. Otherwise, the authentication process falls back to manual (username/password) authentication of the specifiedType. TheTypedoesn’t have to be Kerberos. To change this behavior so that users can authenticate only using Kerberos, setUse Default Authentication on Kerberos Authentication FailuretoNoin a GlobalProtect portal agent configuration.
- (LDAP only) EntersAMAccountNameas theLogin Attribute.
- (LDAP only) Set thePassword Expiry Warningto specify the number of days before password expiration that users will be notified. By default, users will be notified seven days prior to password expiration (range is 1-255). Because users must change their passwords before the end of the expiration period, make sure you provide a notification period that is adequate for your user base to ensure continued access to the VPN. To use this feature, you must specify one of the following types of LDAP servers in your LDAP server profile:active-directory,e-directory, orsun.Users cannot access the VPN if their passwords expire unless you enable pre-logon.
- Select theAdvancedtab.
- In the Allow List,Addand then select the users and groups that are allowed to authenticate with this profile. Selecting the predefinedalloption allows every user to authenticate. By default, the list has no entries, which means no users can authenticate.
- Commit the configuration.
Recommended For You
Recommended videos not found.