Remote Access VPN (Authentication Profile)
In the GlobalProtect VPN for Remote Access, the GlobalProtect portal and gateway are configured on ethernet1/2, so this is the physical interface where GlobalProtect users connect. After a user connects and authenticates to the portal and gateway, the endpoint establishes a tunnel from its virtual adapter, which has been assigned an IP address from the IP pool associated with the gateway tunnel.2 configuration—10.31.32.3-10.31.32.118 in this example. Because GlobalProtect VPN tunnels terminate in a separate corp-vpn zone, you have visibility into the connection traffic as well as the ability to customize security policies for remote users.
Interfaces and Zones for GlobalProtect.Use the default virtual router for all interface configurations to avoid having to create inter-zone routing.
- Select NetworkInterfacesEthernet. Configure ethernet1/2 as a Layer 3 Ethernet interface with IP address 203.0.113.1, and then assign it to the l3-untrustSecurity Zone and the default Virtual Router.
- Create a DNS “A” record that maps IP address 203.0.113.1 to gp.acme.com.
- Select NetworkInterfacesTunnel and Add the tunnel.2 interface. Add the tunnel interface to a new Security Zone called corp-vpn, and then assign it to the default Virtual Router.
- Enable User Identification on the corp-vpn zone.
- Create security policies to enable traffic flow between
the corp-vpn zone and the l3-trust zone,
which enables access to your internal resources.
- Select PoliciesSecurity, and then Add a new rule.
- For this example, you would define the rule with the
- Name (General tab)—VPN Access
- Source Zone (Source tab)—corp-vpn
- Destination Zone (Destination tab)—l3-trust
- Use one of the following methods to obtain a server certificate
for the interface hosting the GlobalProtect portal and gateway:Select DeviceCertificate ManagementCertificates to manage certificates as follows:
- Obtain a server certificate. Because the portal and gateway are on the same interface, the same server certificate can be used for both components.
- The CN of the certificate must match the FQDN, gp.acme.com.
- To enable users to connect to the portal without receiving certificate errors, use a server certificate from a public CA.
a server profile.The server profile instructs the firewall on how to connect to the authentication service. Local, RADIUS, Kerberos, SAML, and LDAP authentication methods are supported. This example shows an LDAP authentication profile for authenticating users against the Active Directory.Create the server profile for connecting to the LDAP server (DeviceServer ProfilesLDAP).
Create an authentication profile.Attach the server profile to an authentication profile (DeviceAuthentication Profile).
a GlobalProtect Gateway.Select NetworkGlobalProtectGateways, and then Add the following configuration:Interface—ethernet1/2IP Address—203.0.113.1Server Certificate—GP-server-cert.pem issued by GoDaddyAuthentication Profile—Corp-LDAPTunnel Interface—tunnel.2IP Pool—10.31.32.3 - 10.31.32.118
- Configure the GlobalProtect
Portals.Select NetworkGlobalProtectPortals, and then Add the following configuration:
Up Access to the GlobalProtect Portal:Interface—ethernet1/2IP Address—203.0.113.1Server Certificate—GP-server-cert.pem issued by GoDaddyAuthentication Profile—Corp-LDAP
the GlobalProtect Client Authentication Configurations:Connect Method—On-demand (Manual user initiated connection)External Gateway Address—gp.acme.com
- Set Up Access to the GlobalProtect Portal:
the GlobalProtect App Software.Select DeviceGlobalProtect Client. Follow the procedure to Host App Updates on the Portal.
- (Optional) Enable use of the GlobalProtect mobile
app.Purchase and install a GlobalProtect subscription (DeviceLicenses) to enable use of the app.
- Save the GlobalProtect configuration.Click Commit.
Remote Access VPN (Certificate Profile)
Remote Access VPN (Certificate Profile) With certificate authentication, the user must present a valid client certificate that identifies them to the GlobalProtect portal or gateway. ...
Remote Access VPN with Two-Factor Authentication
Remote Access VPN with Two-Factor Authentication If you configure a GlobalProtect portal or gateway with an authentication profile and a certificate profile (which together can ...
Remote Access VPN with Pre-Logon
Remote Access VPN with Pre-Logon Pre-logon is a connect method that establishes a VPN tunnel before a user logs in. The purpose of pre-logon is ...
Mixed Internal and External Gateway Configuration
Mixed Internal and External Gateway Configuration In a GlobalProtect mixed internal and external gateway configuration, you can configure separate gateways for VPN access and for ...
GlobalProtect Multiple Gateway Configuration
GlobalProtect Multiple Gateway Configuration In the GlobalProtect Multiple Gateway Topology below, a second external gateway is added to the configuration. In this topology, you must ...
Basic LSVPN Configuration with Static Routing
Basic LSVPN Configuration with Static Routing This quick config shows the fastest way to get up and running with LSVPN. In this example, a single ...
GlobalProtect Certificate Best Practices
GlobalProtect Certificate Best Practices The following table summarizes the SSL/TLS certificates you will need, depending on which features you plan to use: Certificate Usage Issuing ...
Prerequisite Tasks for Configuring the GlobalProtect Gateway
Prerequisite Tasks for Configuring the GlobalProtect Gateway Before you can configure the GlobalProtect gateway, you must have completed the following tasks: Create the interfaces (and ...
GlobalProtect Portal for LSVPN Prerequisite Tasks
GlobalProtect Portal for LSVPN Prerequisite Tasks Before configuring the GlobalProtect portal, you must complete the following tasks: Create Interfaces and Zones for the LSVPN on ...