Remote Access VPN (Authentication Profile)

In the Figure: GlobalProtect VPN for Remote Access, the GlobalProtect portal and gateway are configured on ethernet1/2, so this is the physical interface where GlobalProtect clients connect. After a client connects and the portal and gateway authenticates it, the client establishes a VPN tunnel from its virtual adapter, which has been assigned an address in the IP address 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 VPN traffic as well as the ability to customize security policy for remote users.
Figure: GlobalProtect VPN for Remote Access
gp-remote-access-example.png
The following procedure provides the configuration steps for this example. You can also watch the video.
  1. Create Interfaces and Zones for GlobalProtect.
    Use the default virtual router for all interface configurations to avoid having to create inter-zone routing.
    • Select NetworkInterfacesEthernet and configure ethernet1/2 as a Layer 3 Ethernet interface with IP address 203.0.113.1 and assign it to the l3-untrust 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 and add it to a new zone called corp-vpn. Assign it to the default virtual router.
    • Enable User Identification on the corp-vpn zone.
  2. Create security policy to enable traffic flow between the corp-vpn zone and the l3-trust zone to enable access to your internal resources.
    1. Select PoliciesSecurity and then Add a new rule.
    2. For this example, you would define the rule with the following settings:
      • Name—VPN Access
      • Source Zone—corp-vpn
      • Destination Zone—l3-trust
      vpn-policy-example.png
  3. Obtain a server certificate for the interface hosting the GlobalProtect portal and gateway using one of the following methods:
    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 clients to connect to the portal without receiving certificate errors, use a server certificate from a public CA.
  4. Create a server profile.
    The server profile instructs the firewall how to connect to the authentication service. Supported methods are Local, RADIUS, Kerberos, and LDAP authentication. 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).
    server-profile-examle.png
  5. (Optional) Create an authentication profile.
    Attach the server profile to an authentication profile (DeviceAuthentication Profile).
    authentication-profile-example.png
  6. Configure a GlobalProtect Gateway.
    Select NetworkGlobalProtectGateways and add the following configuration:
    Interfaceethernet1/2
    IP Address203.0.113.1
    Server CertificateGP-server-cert.pem issued by GoDaddy
    Authentication ProfileCorp-LDAP
    Tunnel Interfacetunnel.2
    IP Pool10.31.32.3 - 10.31.32.118
  7. Configure the GlobalProtect Portal.
    Select NetworkGlobalProtectPortals and add the following configuration:
    1. Set Up Access to the GlobalProtect Portal. This example uses the following settings:
      Interfaceethernet1/2
      IP Address203.0.113.1
      Server CertificateGP-server-cert.pem issued by GoDaddy
      Authentication ProfileCorp-LDAP
    2. Define the GlobalProtect Agent Configurations using the following settings:
      Connect MethodOn-demand (Manual user initiated connection)
      External Gateway Addressgp.acme.com
  8. Deploy the GlobalProtect Agent Software.
    Select DeviceGlobalProtect Client.
    In this example, use the procedure to Host Agent Updates on the Portal.
  9. (Optional) Enable use of the GlobalProtect mobile app.
    Purchase and install a GlobalProtect Gateway subscription (DeviceLicenses) to enable use of the app.
  10. Save the GlobalProtect configuration.
    Click Commit.

Related Documentation