Captive Portal vs. GlobalProtect: User Authentication and User-ID Mapping

Overview

Palo Alto Networks' PAN-OS offers multiple methods for user authentication and IP-to-username mapping, essential for implementing user-based security policies. Two prominent methods are Captive Portal and GlobalProtect. This document compares these methods, detailing their mechanisms, use cases, and how they contribute to User-ID mappings.

Captive Portal

Captive Portal, also known as Authentication Portal, prompts users to authenticate when their traffic matches specific Authentication Policy rules. It's particularly useful in environments where users are not logged into monitored domains, such as guest networks or non-Windows systems.

Authentication Methods:

Modes of Operation:

Use Cases:

GlobalProtect

GlobalProtect is Palo Alto Networks' VPN solution that provides secure access to enterprise resources. It ensures that user authentication occurs before granting network access, thereby maintaining accurate User-ID mappings.

Authentication Mechanisms:

Deployment Scenarios:

Use Cases:

Comparison Table

Feature Captive Portal GlobalProtect
Authentication Trigger When traffic matches Authentication Policy rules Upon VPN connection initiation
User Experience May require manual login; potential certificate warnings Seamless with SSO; minimal user intervention
Best Suited For Guest users, BYOD environments Remote employees, managed devices
User-ID Mapping Accuracy Dependent on user interaction High accuracy due to enforced authentication
Deployment Complexity Relatively simple Requires client installation and configuration

Mermaid Sequence Diagram: Captive Portal Authentication Flow

sequenceDiagram participant User participant Firewall participant AuthServer User->>Firewall: Accesses web resource Firewall->>User: Redirects to authentication portal User->>Firewall: Submits credentials Firewall->>AuthServer: Validates credentials AuthServer-->>Firewall: Authentication response Firewall->>User: Grants or denies access

Mermaid Sequence Diagram: GlobalProtect Authentication Flow

sequenceDiagram participant User participant GlobalProtect Client participant Portal participant Gateway participant AuthServer User->>GlobalProtect Client: Launches VPN connection GlobalProtect Client->>Portal: Sends authentication request Portal->>AuthServer: Validates user credentials AuthServer-->>Portal: Authentication response Portal->>GlobalProtect Client: Provides configuration and gateway list GlobalProtect Client->>Gateway: Initiates connection Gateway->>AuthServer: Validates user credentials AuthServer-->>Gateway: Authentication response Gateway->>GlobalProtect Client: Establishes VPN tunnel

Authentication Portal Modes: Transparent vs. Redirect

Palo Alto Networks' PAN-OS offers two modes for the Authentication Portal, which determines how the firewall captures web requests for user authentication:

Transparent Mode

Redirect Mode

Mermaid Sequence Diagram: Transparent Mode Authentication Flow

sequenceDiagram participant User participant Firewall participant AuthServer User->>Firewall: Sends HTTP/HTTPS request to destination Firewall->>User: Issues HTTP 401 Unauthorized User->>Firewall: Submits credentials Firewall->>AuthServer: Validates credentials AuthServer-->>Firewall: Authentication response Firewall->>User: Grants or denies access

Mermaid Sequence Diagram: Redirect Mode Authentication Flow

sequenceDiagram participant User participant Firewall participant AuthPortal participant AuthServer User->>Firewall: Sends HTTP/HTTPS request to destination Firewall->>User: Issues HTTP 302 Redirect to AuthPortal User->>AuthPortal: Accesses authentication portal AuthPortal->>User: Presents login page User->>AuthPortal: Submits credentials AuthPortal->>AuthServer: Validates credentials AuthServer-->>AuthPortal: Authentication response AuthPortal->>User: Grants or denies access

References