A controller module that allows a hotspot user to enter his or her
hotspot user name and password to gain access to the hotspot portal
(either through browser-based logon or Smart Client logon).
Subscriber Portal
A user who has passed the authentication processAuthenticated user
A user who has not passed the authentication process or has failed
authentication
Unauthenticated user
The purpose of the walled garden is to let unauthenticated users
access online registration, payment services, or other websites (such
Walled garden
as a hotel reservation page) without needing to log on first. All other
sites are off-limits.
How Hotspot Authentication Works
This section describes the steps that a hotspot user performs to gain access to the hotspot
portal and how the controller handles the hotspot access request.
NOTE: Ruckus Wireless hotspot portals are based on the Wireless Internet Service Provider
roaming (WISPr) standards.
1. A hotspot client associates with the hotspot WLAN service (which is typically unencrypted)
that is provided by a Ruckus Wireless AP.
NOTE: The hotspot modules – Captive Portal and Subscriber Portal – communicate with the
AP through the user defined interface (if configured) or the control Interface. For information
on creating a user defined interface, refer to Creating a User Defined Interface on page 277.
2. The hotspot user attempts to browse the Web (for example, www.ruckuswireless.com) on
the hotspot client.
3. The AP detects the user state (which, in this case, is unauthenticated) and performs network
address translation (NAT) to the related port on the Captive Portal. The AP also adds
information to the HTTP header, including the AP SSID and device MAC address and IP
address.
4. The Captive Portal module first applies the blacklist user-agent (see User Agent Blacklist on
page 274), and then the walled garden list to the request (URL whitelist, only for UEs configured
with web proxy. The AP handles the walled garden for non-web proxy UEs). If the request
passes these two filters, the Captive Portal redirects the hotspot user to the configured portal
URL. In case it was configured as an internal portal, the Subscriber Portal module handles
the request and displays the hotspot logon page.
NOTE: The controller provides a built-in Subscriber Portal module that you can use
immediately.
5. The hotspot user enters the user name and password provided by the hotspot operator on
the logon page that is presented by the Subscriber Portal.
SmartCell Gateway 200/Virtual SmartZone High-Scale for Release 3.4.1 Administrator Guide
268
Creating and Managing Hotspots
How Hotspot Authentication Works
To Next Page
Loading...
