Which authentication does Aruba's Captive Portal use?

Aruba’s Captive Portal uses Layer 3 authentication, which means that it intercepts the client’s HTTP

requests and redirects them to a web page where the client can enter their credentials. The

credentials are then verified by a RADIUS server or a local database before granting network access.

Reference: https://www.arubanetworks.com/techdocs/Instant_86_WebHelp/Content/instantug/captive-portal/captive-portal-auth.htm

Aruba's Captive Portal primarily uses Layer 3 authentication, which operates at the network layer.

When a user connects to a network with a Captive Portal, they are redirected to a web page for

authentication. This process involves the user entering credentials or accepting terms and conditions

through a web interface before gaining full access to the network. The Captive Portal intercepts the

user's web traffic at Layer 3, requiring them to authenticate before proceeding, which is why it's

considered a form of Layer 3 authentication.