Enable Two-Factor Authentication Using Certificate and Authentication
The following workflow describes how to configure GlobalProtect client authentication requiring the user to authenticate both to a certificate profile and an authentication profile. The user must successfully authenticate using both methods in order to connect to the portal/gateway. For more details on this configuration, see Remote Access VPN with Two-Factor Authentication.
- Create an authentication server profile.The authentication server profile determines how the firewall connects to an external authentication service and retrieves 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 a profile type (DeviceServer ProfilesLDAP,Kerberos,RADIUS, orTACACS+).
- Adda new server profile.
- Enter aProfileNamefor the profile, such as GP-User-Auth.
- (LDAP only) Select theTypeof LDAP server (active-directory,e-directory,sun, orother).
- ClickAddin the Servers list section and then enter the required information for connections to the authentication service, including the serverName, IP address or FQDN of theServer, andPort.
- (RADIUS, TACACS+, and LDAP only) Specify settings to enable the firewall to authenticate to the authentication service as follows:
- RADIUS and TACACS+—Enter the sharedSecretwhen adding the server entry.
- LDAP—Enter theBind DNandPassword.
- (LDAP only) If you want the endpoint 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 serverPortin theServer list:
- Any other port—The device first attempts to use TLS. If the directory server does not support TLS, the device uses SSL.
- (LDAP only) For additional security, select theVerify Server Certificate for SSL sessionscheck box so that the endpoint verifies the certificate that the directory server presents for SSL/TLS connections. To enable verification, you also must select theRequire SSL/TLS secured connectioncheck box. For verification to succeed, one of the following conditions must be true:
- The certificate is in the list of device certificates:. Import the certificate into the endpoint 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.
- Create an authentication profile that identifies the service for authenticating users. (You later have the option of assigning the profile on the portal and on gateways.)
- SelectandDeviceAuthentication ProfileAdda new profile.
- Enter aNamefor the profile.
- Select theLocation.
- Select theTypeofAuthentication(LDAP,Kerberos,RADIUS, orTACACS+).
- Select theServer Profileyou created in 1.
- (LDAP only) EntersAMAccountNameas theLogin Attribute.
- ClickOKto save the authentication profile.
- Create a client certificate profile that the portal uses to authenticate the client certificates that come from user devices.When you configure two-factor authentication to use client certificates, the external authentication service uses the username value to authenticate the user, if specified, in the client certificate. This ensures that the user who is logging is in is actually the user to whom the certificate was issued.
- Selectand clickDeviceCertificatesCertificate ManagementCertificate ProfileAddand enter a profileName.
- Select a value for theUsername Field:
- If you intend for the client certificate to authenticate individual users, select the certificate field that identifies the user.
- If you are deploying the client certificate from the portal, leave this field set toNone.
- If you are setting up a certificate profile for use with a pre-logon connect method, leave the field set toNone.
- In theCA Certificatesarea, clickAddand then:
- Select theCA certificate, either a trusted root CA certificate or the CA certificate from a SCEP server. (If necessary, import the certificate).
- (Optional) Enter theDefault OCSP URL.
- (Optional) Select a certificate forOCSP Verify CA.
- (Optional) Select options that specify when to block the user’s requested session:
- Status of certificate is unknown.
- GlobalProtect component does not retrieve certificate status within the number of seconds inCertificate Status Timeout.
- To transparently deploy client certificates, configure your portal to distribute a shared client certificate to your endpoints or configure the portal to use SCEP to request and deploy unique client certificates for each user.
- Use your enterprise PKI or a public CA to issue a client certificate to each GlobalProtect user.
- For the pre-logon connect methods, install certificates in the personal certificate store on the client systems.
- Save the GlobalProtect configuration.ClickCommit.
Recommended For You
Recommended videos not found.