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
 
The script on the ECP that receives redirected requests has two responsibilities:
• Parse the redirection URL and preserve critical parameters for future use.
• Compose the web page that the user fills in to log into the network.
The Redirection URL Sent from Extreme Campus Controller
The request for the login page is in the form of an HTTP/HTTPS GET request. All the arguments to the
request are passed as query strings appended to the URL. Typically, the web server or the back-end
runtime system will parse the query strings and make them available to the back-end scripts.
The parameters that are described in Table 11 on page 95 are included in the URL statement sent from
Extreme Campus Controller. The following parameters are required to be included in the return
statement to Extreme Campus Controller:
• wlan
• token
• role
• user name
• password
Additional parameters are provided optionally for reporting purposes.
Table 11: Parameters Available on the Redirection URL from Extreme Campus
Controller to the ECP
Parameter
Name
Parameter Value Required Notes
ap No The AP Name to which the authenticating user
has associated.
bssid Alphanumeric
String
No The BSSID to which the authenticating client has
associated. The BSSID is a MAC address
belonging to the AP to which the client
associated. The BSSID is in the format of six hex
digits. The hex digits are “0123456789abcdef”.
An example BSSID could be “00026fe9b568”.
This is the same value that would be included in
the Called-Station-ID field of a RADIUS Access-
Request sent on behalf of this client.
ssid A character string
up to 32 bytes
long
No The SSID (Service Set Identifier) to which the
client associated. ASCII-encoded hex string.
dest Alphanumeric
string
No This is the original URL that the client’s browser
was trying to receive when the request was
redirected. The string is URI-encoded. For
example, slashes in the URL are replaced by
“%2F”.
External Captive Portal on a Third-Party Server
The Redirection URL Sent from Extreme Campus
Controller
Extreme Campus Controller Deployment Guide for version 5.46.03 95










