Web / RADIUS flow

What happens in practice.

Short version: web redirect first, optional RADIUS backend second.

1

Guest opens a web page. The device redirects to the portal.

2

The portal checks the local ticket or user.

3

If enabled, credentials are synced or checked through RADIUS.

4

The controller accepts the login and the event is logged.

Web flow

The portal host handles the captive redirect and guest login page.

RADIUS option

Use RADIUS when you want backend authentication or synchronized credentials.