Sign visitors in through a hosted WiFi login page
For controllers with a captive portal, such as Ruckus Cloudpath: visitors join the guest network and a branded Offision login page in their browser checks their visit before letting them online.
Connect a captive-portal WiFi controller to Offision’s hosted OAuth 2.0 login page so checked-in visitors can sign in through their browser using the credentials on their badge. When a visitor joins the guest network, the portal opens your branded Offision login page and verifies their active visit before granting internet access.
1. Add a Ruckus Cloudpath network entry
Open Visitor WiFi, select Add, and choose Ruckus Cloudpath from the brand menu. Selecting the brand creates a draft entry immediately to generate its OAuth client, so closing the dialog without saving leaves the draft entry in the list.
On the Basic page, fill in these settings:
- WiFi SSID: Enter the exact network name broadcast by your controller. Offision prints this name on visitor badges and displays it on lobby boards.
- WiFi password: Enter the pre-shared key if visitors need a network password before the captive portal opens.
- Username type and Password type: Choose which visit credentials visitors enter on the login page. See the Visitor WiFi settings reference for every field.
The Basic page of a Ruckus Cloudpath entry includes the WiFi SSID field.
2. Copy the OAuth values into your captive portal
Open OAuth Config on the second page of the dialog. Copy each generated value into your controller’s Custom OAuth 2.0 settings: Consumer key (Client ID), Consumer secret (Client Secret), Access token endpoint URL, Authorize URL, Data URL, and Scope.
The OAuth Config page provides a copy button for each connection value.
Next, paste your captive portal’s callback address into OAuth redirect URL. Sign-in fails if the redirect URL is missing.
3. Customize the hosted WiFi login page
Open WiFi login page on the third page of the dialog to brand the browser page visitors see: Logo, Page title, Welcome message, Footer text, and Background Image. You can enter translations for each enabled language.
The WiFi login page tab lets you customize the browser sign-in screen.
Use Welcome message to tell visitors where to find their sign-in details on their badge.
The hosted login page labels the first input field according to your selected Username type.
4. Point your captive portal to the OAuth configuration
On your WiFi controller, assign the guest SSID’s captive portal to the OAuth 2.0 configuration from step 2 so joining visitors are redirected to Offision’s login page.
5. Test check-in and check-out access
Check in a test visitor, join the guest SSID, and wait for the browser login page to open. Sign in with the badge details. The login form names the username field after your Username type (for example, Visitor code when using the registration code). Confirm internet access works, then check the visitor out and verify that sign-in is refused.
Troubleshooting the WiFi login page
| Symptom | Cause |
|---|---|
| The login page never opens | The captive portal redirect does not point to the OAuth sign-in configuration, or OAuth redirect URL is missing on the Offision entry. |
| Sign-in is refused for a real visitor | The visitor has not checked in yet, or their visit period has ended. |
| Every sign-in is refused | The entry has no Visitor WiFi Integration license, or the captive portal still holds an old client secret. |
| The badge prints the wrong network name | WiFi SSID on the Offision entry does not match the SSID broadcast by your controller. |