An organization is setting up a guest network using ClearPass and wants to ensure a seamless login experience for repeat visitors. Which approach should they take to achieve this goal while maintaining a reasonable level of security?

To create a seamless login experience for repeat guest visitors, combining MAC authentication with the captive portal is the standard and most effective method. On a guest's first visit, they authenticate through the captive portal, and ClearPass records their device's MAC address. For subsequent connections, a MAC authentication service identifies the known device and allows it on the network without redirecting to the login page. This process, often called MAC caching, provides convenience for returning users while maintaining initial registration security.

A: A full 802.1X implementation is too complex for a typical guest environment, requiring supplicants and credentials that guests do not have. C: A web login page alone requires guests to manually authenticate every time they connect, which is the opposite of a seamless experience.

- Aruba ClearPass Deployment Guide, Version 6.7, page 138, "Guest Access with MAC Caching": "The workflow for guest access with MAC caching is as follows: 1. The user connects and is redirected to a Web Login page... 3. On subsequent authentications, the user’s MAC address is known and they are allowed on the network."

- ClearPass Policy Manager 6.9 User Guide, page 1, "Service Templates": Describes the "Guest MAC Authentication" service template used for this purpose.