Deployment Guide
Table Of Contents
- Table of Contents
 - Preface
 - About Extreme Campus Controller Deployment
 - Configuring DHCP, NPS, and DNS Services
 - Centralized Site with a Captive Portal
 - Centralized Site with AAA Network
 - Deploying a Mesh Network
 - Configuring an External NAC Server for MBA and AAA Authentication
 - Manage RADIUS Servers for User Authentication
 - External Captive Portal on a Third-Party Server
 - Access Control Rule Admin Portal Access
 - Deploying Centralized Web Authentication
 - Deploying ExtremeCloud IQ - SE as an External Captive Portal
- Deployment Strategy
 - Configuring an External Captive Portal Network
 - Editing the Configuration Profile for Network and Roles
 - Extreme Campus Controller Default Pass-Through Rule
 - Adding Extreme Campus Controller as a Switch to ExtremeCloud IQ - Site Engine
 - Editing the Unregistered Policy on ExtremeCloud IQ - Site Engine
 - Editing the ExtremeCloud IQ - Site Engine Profile for Policy and Location-Based Services
 
 - Deploying an ExtremeGuest Captive Portal
 - Deploying Client Bridge
 - Deploying an Availability Pair
 - Deploying Universal APs
 - Extreme Campus Controller Pair with ExtremeLocation and AirDefense
 - ECP Local Authentication
 - PHP External Captive Portal, Controller’s Firewall Friendly API
 - Index
 
External Captive Portal on a Third-Party
Server
Firewall Friendly External Captive Portal Flow of Events on page 92
Configure the Firewall on page 94
Configure an External Captive Portal on page 94
Understand Processing Performed by the ECP on page 94
Approve the Client on page 105
Compose the Redirection Response Sending the Browser back to the Appliance
on page 106
Extreme Campus Controller supports integration with an External Captive Portal (ECP) on a third-party
server.
An ECP is a web server that hosts a site that allows users to authenticate to the network. When the web
server is not hosted on Extreme Campus Controller, the captive portal is considered a third-party ECP.
Extreme Campus Controller intercepts and redirects the user’s HTTP messages to the ECP web server.
ECP authentication involves filtering trac of unauthenticated clients. When the client sends HTTP
trac, its browser is redirected to a website where the client’s user can authenticate. The website is
referred to as an ECP because it is located outside Extreme Campus Controller (which also oers an
‘internal’ captive portal). The ECP authenticates the user in whatever way it sees fit, and then tells
Extreme Campus Controller or the AP whether the user is authenticated and what policy to apply to the
user’s session.
All interactions with the ECP are initiated by the user. The enterprise allows sta and guests to egress
through port 80 on the firewall to use the third-party ECP.
We will discuss how to configure and program the ECP to interact with Extreme Campus Controller. This
includes details about the message sequence that occurs when a client authenticates through an ECP.
The following authentication flows are supported:
• A simplified flow in which Extreme Campus Controller accepts instructions from the ECP relayed
through the client web browser.
• A more complex flow in which Extreme Campus Controller invokes RADIUS authentication to
confirm the apparent authentication status of the client.
Extreme Campus Controller Deployment Guide for version 5.46.03
91










