Enable Authentication Using a Certificate Profile
The following workflow shows how to enable authentication for strongSwan clients using a certificate profile.
- Configure an IPSec tunnel for the GlobalProtect gateway for communicating with a strongSwan client.
- Selectand then select the gateway name.NetworkGlobalProtectGateways
- Select theCertificate Profileyou want to use for authentication in theAuthenticationtab.
- Selectand specify the following settings to set up a tunnel:AgentTunnel Settings
- Select the check box toEnable X-Auth Support.
- If aGroup NameandGroup Passwordare already configured, remove them.
- ClickOKto save the settings.
- Verify that the default connection settings in theconn %defaultsection of the IPSec tunnel configuration file (ipsec.conf) are correctly defined for the strongSwan client.Theipsec.conffile is usually found in the/etcfolder.The configurations in this procedure are tested and verified for the following releases:
The configurations in this procedure can be used for reference if you are using a different version of strongSwan. Refer to the strongSwan wiki for more information.Modify the following settings in theconn %defaultsection of theipsec.conffile to these recommended settings.ikelifetime=20m reauth=yes rekey=yes keylife=10m rekeymargin=3m rekeyfuzz=0% keyingtries=1 type=tunnel
- Ubuntu 14.0.4 with strongSwan 5.1.2 and CentOS 6.5 with strongSwan 5.1.3 for PAN-OS 6.1.
- Ubuntu 14.0.4 with strongSwan 5.2.1 for PAN-OS 7.0.
- Modify the strongSwan client’s IPSec configuration file (ipsec.conf) and the IPSec password file (ipsec.secrets) to use recommended settings.Theipsec.secretsfile is usually found in the/etcfolder.Use the strongSwan client username as the certificate’s common name.Modify the following items in theipsec.conffile to these recommended settings.conn <connection name> keyexchange=ikev1 authby=rsasig ike=aes-sha1-modp1024,aes256 left=<strongSwan/Linux-client-IP-address> leftcert=<client certificate with the strongSwan client username used as the certificate’s common name> leftsourceip=%config leftauth2=xauth right=<GlobalProtect-Gateway-IP-address> rightid=“CN=<Subject-name-of-gateway-certificate>” rightsubnet=0.0.0.0/0 auto=addModify the following items in theipsec.conffile to these recommended settings.:RSA <private key file> “<passphrase if used>”
- Start strongSwan IPSec services and connect to the IPSec tunnel that you want the strongSwan client to use when authenticating to the GlobalProtect gateway.Use theconfig <name>variable to name the tunnel configuration.
- Ubuntu clients:ipsec start ipsec up <name>
- CentOS clients:strongSwan start strongswan up <name>
- Verify that the tunnel is set up correctly and the VPN connection is established to both the strongSwan client and the GlobalProtect gateway.
- Verify the detailed status information on a specific connection (by naming the connection) or verify the status information for all connections from the strongSwan client:
- Ubuntu clients:ipsec statusall [<connection name>]
- CentOS clients:strongswan statusall [<connection name>]
- Select. Then, in the Info column, selectNetworkGlobalProtectGatewaysRemote Usersfor the gateway configured for the connection to the strongSwan client. The strongSwan client should be listed underCurrent Users.
Enable Authentication Using an Authentication Profile
Enable Authentication Using an Authentication Profile The following workflow shows how to enable authentication for strongSwan clients using an authentication profile. The authentication profile specifies ...
Enable Authentication Using Two-Factor Authentication
Enable Authentication Using Two-Factor Authentication With two-factor authentication, the strongSwan client needs to successfully authenticate using both a certificate profile and an authentication profile to ...
Set Up Authentication for strongSwan Ubuntu and CentOS Clients
Set Up Authentication for strongSwan Ubuntu and CentOS Clients To extend GlobalProtect VPN remote access support to strongSwan Ubuntu and CentOS clients, set up authentication ...
Authentication The GlobalProtect™ portal and gateway must authenticate the end-user before it allows access to GlobalProtect resources. You must configure authentication mechanisms before continuing with ...
Configure a GlobalProtect Gateway
Configure a GlobalProtect gateway to enforce security policies and provide VPN access for your users. ...
Tunnel Settings Tab
Tunnel Settings Tab Select Network GlobalProtect Gateways Agent Tunnel Settings to enable tunneling and configure the tunnel parameters. Tunnel parameters are required if you are ...
About GlobalProtect Cipher Selection
About GlobalProtect Cipher Selection GlobalProtect supports both IPSec and SSL tunnel modes. GlobalProtect also supports the ability to enable and require the GlobalProtect agent to ...
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 ...
Determine the Ciphers Used to Setup IPSec Tunnels
Ciphers Used to Set Up IPSec Tunnels GlobalProtect can restrict and/or set preferential order for what encryption and authentication algorithm the GlobalProtect agent can use ...