Wireless Access

Starting from ArubaOS 8.7.0.0, Captive Portal Authentication in Bridge Mode can be enabled with ageout-bridge-user.

1) Since Captive portal authentication is L3 authentication, can anyone explain how the "ageout-bridge-user" mechanism works?

2) Any other requirement to allow bridge mode captive portal to works?

That forces an ageout behavior for bridged clients to prevent sessions being held open without a connected client.

The captive portal workflow must be server based, i.e., uses a CoA call to move the user session from redirected to not.