With Aruba Cloud Guest, visitors report the captive portal keeps appearing after devices sleep. Which solution should be enabled to address this?

With Aruba Cloud Guest, visitors report the captive portal keeps appearing after devices sleep. Which solution should be enabled to address this?

• A. MAC Caching under the splash page
• B. MAC Caching under the user-role
• C. Wireless Caching under the splash page
• D. MAC Caching under the WLAN

Answer: (A)

When a guest device reconnects after sleeping, the captive portal can trigger again if the device isn’t recognized as already authenticated. Caching the MAC address at the splash page ties the device’s identity directly to the captive portal session. Once the guest device has been authenticated, Aruba stores its MAC in the splash page cache, so on subsequent wake-ups or re-connections the system recognizes the device and bypasses showing the portal again for the duration of the cache. This provides seamless access for visitors without repeatedly returning to the login screen. Caching under the user-role would rely on the user credentials rather than the device identity, which isn’t as reliable for guest devices that may reconnect without re-entering credentials. Caching under the WLAN or using a broader “wireless caching” path wouldn’t specifically preserve the captive portal state for the guest session in the same targeted way, so they’re less effective for this scenario.

When a guest device reconnects after sleeping, the captive portal can trigger again if the device isn’t recognized as already authenticated. Caching the MAC address at the splash page ties the device’s identity directly to the captive portal session. Once the guest device has been authenticated, Aruba stores its MAC in the splash page cache, so on subsequent wake-ups or re-connections the system recognizes the device and bypasses showing the portal again for the duration of the cache. This provides seamless access for visitors without repeatedly returning to the login screen.

Caching under the user-role would rely on the user credentials rather than the device identity, which isn’t as reliable for guest devices that may reconnect without re-entering credentials. Caching under the WLAN or using a broader “wireless caching” path wouldn’t specifically preserve the captive portal state for the guest session in the same targeted way, so they’re less effective for this scenario.