Captive Portal Workflows and VSA
This section describes the workflow of the captive portal and VSA.
Successful Captive Portal Authentication
Captive portal authentication workflow describes the workflow where the external portal sends
a message to the controller to initiate RADIUS authentication to complete the portal authentication
procedure.
1. The UE associated controller triggers MAC based authentication, which is rejected by the
AAA server since the UE MAC is not registered.
2. A DHCP procedure is triggered and the IP address is allocated from the DHCP server.
3. When the UE tries to browse a DNAT procedure is performed at the data plane since the
user is not yet authenticated.
4. The user is redirected to login page of the external portal.
5. On user entering his login credentials the external portal calls the controller's API (NBI API)
to complete the authentication procedure
6. The controller triggers the RADIUS CHAP authentication towards the AAA server.
7. On successful authentication the user is disassociated. This complete the UE registration
procedure with external AAA server.
8. The UE re-associates to the AP.
9. MAC authentication is triggered by the controller. The AAA server responds with access
accept with IMSI, MSISDN, QoS (optional) and APN (optional).
SmartCell Gateway 200/Virtual SmartZone High-Scale for Release 3.4.1 Administrator Guide
401
Overview of the Captive Portal
Captive Portal Workflows and VSA
To Next Page
Loading...
