Symantec VIP Enterprise Gateway Authentication with EAP/TTLS
search cancel

Symantec VIP Enterprise Gateway Authentication with EAP/TTLS

book

Article ID: 433766

calendar_today

Updated On:

Products

VIP Service

Issue/Introduction

This document provides guidance for VIP customers who are currently using VIP Enterprise Gateway (EG) for RADIUS-based authentication when their client application (such as VPN clients, 802.1X wireless, or network access controllers) requires EAP (Extensible Authentication Protocol) support.

For your reference, an alternative approach to EAP/RADIUS is included to address this requirement when the VIP Enterprise Gateway (RADIUS) is not in use.

Resolution

VIP Enterprise Gateway 9.11.3 provides robust RADIUS-based authentication supporting PAP (Password Authentication Protocol) and EAP (Extensible Authentication Protocol) through the IKEv2 standard. 

VIP Enterprise Gateway RADIUS Validation Server with EAP-TTLS Architecture Overview:

When establishing a connection, the VPN Gateway (Palo Alto, FortiGate, etc.) acts as an Authenticator / Network Access Server (NAS) that proxies EAP messages between the VPN Client and the VIP Enterprise Gateway.

  1. The VPN client initiates an outer connection request via IKEv2 to the VPN Gateway.
  2. The VPN Gateway prompts the client for identity via EAP-Request.
  3. The VPN Client responds with an outer / anonymous identity (e.g., [email protected]).
  4. The VPN Gateway forwards this to the VIP Enterprise Gateway RADIUS validation server inside a RADIUS Access-Request.
  5. The VIP Enterprise Gateway initiates a TLS handshake with the VPN client through the VPN Gateway.
  6. The VIP Enterprise Gateway presents the EAP-TTLS certificate in the Validation Server settings directly to the VPN client for validation.
  7. Once validated, a secure, encrypted TLS Tunnel is established directly between the VPN Client and VIP Enterprise Gateway. 
  8. The VPN client sends the actual user credentials though the secure TLS Tunnel to the VIP Enterprise Gateway using the PAP authentication protocol.
  9. The VIP Enterprise Gateway validates the inner credentials against the Symantec VIP Service (Username-OTP mode) and LDAP/Active Directory (Username-Password-OTP mode).
  10. Upon successful authentication, the VIP Enterprise Gateway responds with a RADIUS Access-Accept message to the VPN Gateway.
  11. The VPN Gateway completes the VPN connection setup, assigns an IP address/virtual adapter to the VPN client, and opens the secure VPN tunnel for network traffic.

Benefits:

  • EAP-TTLS Protocol Support: Implements RFC 5281 compliant EAP-TTLS with TLS tunnel establishment
  • Inner PAP Authentication: Username and password securely transmitted inside encrypted TLS tunnel
  • VIP Integration: Supports VIP authentication methods, such as OTP and PUSH
  • TLS Security: Certificate-based server authentication with configurable TLS versions (TLS 1.2+)
  • Session Management: Efficient handling of concurrent EAP sessions with automatic cleanup
  • Backward Compatible: Existing PAP authentication continues to work unchanged

Requirements:

  • VIP Enterprise Gateway 9.11.3.
  • A VPN client configured for IKEv2. The VPN client must be an EAP-TTLS capable RADIUS client (VPN, 802.1X)
  • Wireless networks using 802.1X authentication (WPA2-Enterprise, WPA3- Enterprise)
  • Network Access Control (NAC) systems enforcing EAP-based authentication

EAP/TTLS Certificate Requirements on the VIP Enterprise Gateway:

  • The server certificate must include the Server Authentication Extended Key Usage (EKU) attribute.
  • Must contain the public and private keys in PKCS12/PFX format.
  • The Subject Alternative Name (SAN) value should be set to the Fully Qualified Domain Name (FQDN) of the VIP Enterprise Gateway server.
  • ECDSA certificates offer faster handshakes, smaller file sizes, and lower system resources.
  • The VPN client device must have the corresponding root and intermediate CA certificates installed in its trust store. The EAP/TTLS certificate is not installed on the VPN Client. 

Limitations:

  • RADIUS Access-Challenge and PUSH number challenge is not supported in the EAP-TTLS/PAP framework. The VPN Client should not prompt users for additional input after the initial authentication. The following inline MFA methods are supported:
    • Username and OTP (UO mode)
    • Username and Password+OTP (ULO mode)
    • Username and Password with PUSH authentication
  • RADIUS with EAP-TTLS can increase the Validation Server CPU consumption due to the asymmetric cryptography involved in establishing the connection. 

Additional Information:

 

 

Alternate Option: ENTRA ID / Azure SAML Integration (No RADIUS or EAP)

Overview:

Customers with an active Entra ID/Azure AD tenant and an active VIP Manager tenant can utilize SAML-based authentication as an alternative, non-RADIUS option by leveraging Azure/Entra ID as an identity provider to provide modern authentication protocols for supported clients.

Benefits: 

  • SAML 2.0 Protocol: Industry-standard federation protocol for web-based authentication.
  • VIP Federation: Azure AD federates to VIP Cloud for MFA enforcement.
  • No RADIUS Required: Eliminates the VIP Enterprise Gateway RADIUS infrastructure dependency entirely
  • Browser-Based Authentication: Native support for web applications and portals.
  • Modern MFA Support: Supports FIDO2/WebAuthn alongside OTP and PUSH notifications.
  • Cloud-Native: Fully cloud-based solution with no on-premises components required.

Prerequisites:

  • Active Microsoft Entra ID/Azure AD tenant (P1 or P2 license recommended)
  • Client application must support SAML 2.0 authentication
  • Active VIP Manager tenant

Architecture Overview:

Architectural flow using Microsoft Entra ID over SAML.

 



Additional Information

Fortinet FortiClient EAP Authentication.