FAQ
Short notes on portal operation, RADIUS rollout, tenants, logs, SMS and security.
It covers branded captive portal pages, ticket creation, print/PDF handling, email delivery, optional SMS self-registration, tenant administration, RADIUS device management, online users, logs, CSV exports and change history.
FortiGate, Cisco, Ubiquiti and Aruba configuration paths are represented. FortiGate and Cisco are the most deeply validated, including Cisco CWA and FreeRADIUS apply workflows.
Guests are redirected to the portal, authenticate with a voucher or SMS flow, and the controller grants access through the configured web or RADIUS path. RADIUS devices can be prepared with dry-run, diff review and masked-secret apply output.
Yes. The RADIUS/NAD workflow includes dry-run and diff output for generated FreeRADIUS clients and Cisco CWA policy files. Shared secrets are masked, and apply results are recorded in change history.
Filtered Online Users, RADIUS Logs, SMS Logs, System Logging and Change History views can be exported as CSV while keeping the same tenant scope and filters as the UI.
Tenant admins operate inside their assigned tenant. Global admins can switch context, use global views, filter by tenant and export centrally without changing the tenant isolation used by the UI.
SMS self-registration and SMS logging are available as tenant operations. Gateways can be configured per tenant, and delivery attempts are visible in the SMS dashboard and logs.
Plain HTTP is not encrypted. Some captive portal redirects still need HTTP compatibility for the first handoff, while admin access and the public website are intended to run on HTTPS.
RADIUS packets, accounting sessions, Wi-Fi activity, SMS delivery, email delivery, system events and administrative changes are visible through the admin operations screens.
Run the app checks, confirm database and vault configuration, verify RADIUS target paths, test dry-run/apply, and smoke-test the admin and portal hosts after deployment.