Captive Portal Detection
UXI hardware sensors implement Captive Portal Discovery and Captive Portal Identification to determine if the device is behind a captive portal.
The sensor will send an HTTP request to http://cdn.capenetworks.io/auth expecting a 200 response code with Success in the response body. If the sensor receives any unexpected response it will consider this as the presence of a captive portal and/or proxy.
Alternatively, if the configured network supports RFC8910 or RFC8908, then the sensor will query the captive portal API endpoint that is reported in the DHCPv4 lease, DHCPv6 lease or Router Advertisement packet for IPv6.
Captive Portal Interaction
In order for a sensor to test a captive portal, a recording of user actions required to navigate the portal must be provided to the Aruba UXI support team.
Prerequisites:
Before starting make sure that you have configured the SSID on the dashboard and have assigned the SSID to one or more sensors.
To correctly configure a captive portal, support will need the following details:
An Aruba Recorder output (.fside) file.
The SSID for which the Captive Portal is for.
The sensor serial(s).
Note:
If your captive portal requires login credentials, please create a service account specifically for the sensors to test. Using personal credentials is not recommended.
The process to record user actions is as follows:
Install the Aruba Recorder tool from the Chrome Web Store
Make sure you are connected to the correct WiFi SSID, but not authenticated to the portal
Open Chrome
Click on the Aruba Recorder extension icon (the green smiley face)
Click the Record button, which will open a new window and show the captive portal
Log in to the captive portal
Click the Aruba Recorder extension icon again, and click the Stop button
Find the side-recording.json file in your downloads
To make sure that you have recorded the interaction correctly you can open the file and check if commands like click, type, etc. are recorded under the "Commands" section. If it's empty then you will need to record it again. Example output:
..........
{
"id": "cfcfdf76-48a4-4cc0-8655-3c0f8b3d9879",
"name": "Captive Portal Test",
"commands": [
{
"command": "click",
"target": "id=email_field",
"targets": [
[
"................
Lastly, you will need to contact support@capenetworks.com and include the sensor serial, the name of the SSID, and the recording output file.