In an AOS-8 mobility architecture, the Mobility Controller (MC) manages user roles and policies for wireless clients connecting to SSIDs. When a user connects to an SSID with WPA3-Enterprise security, the MC uses 802.1X authentication to validate the user against an authentication server, in this case, HPE Aruba Networking ClearPass Policy Manager (CPPM). The SSID is configured with specific roles:
Initial role: Applied before authentication begins (not specified in the question, but typically used for pre-authentication access).
Logon role: Applied during the authentication process to allow access to authentication services (e.g., DNS, DHCP, or RADIUS traffic).
802.1X default role (guest): Applied if 802.1X authentication fails or if no specific role is assigned by the RADIUS server after successful authentication.
In this scenario, the user successfully authenticates, and CPPM sends an Access-Accept message with an Aruba-User-Role Vendor-Specific Attribute (VSA) set to "contractor." The "contractor" role exists on the MC, meaning it is a predefined role in the MC’s configuration.
When the MC receives the Aruba-User-Role VSA, it applies the specified role ("contractor") to the user session, overriding the default 802.1X role ("guest"). The MC does not combine the contractor role with other roles like logon or guest; it applies only the role specified by the RADIUS server (CPPM) in the Aruba-User-Role VSA. This is the standard behavior in AOS-8 for role assignment after successful authentication when a VSA specifies a role.
Option A, "Applies the rules in the logon role, then guest role, and the contractor role," is incorrect because the MC does not apply multiple roles in sequence. The logon role is used only during authentication, and the guest role (default 802.1X role) is overridden by the contractor role specified in the VSA.
Option C, "Applies the rules in the contractor role and the logon role," is incorrect because the logon role is no longer applied once authentication is complete; only the contractor role is applied.
Option D, "Applies the rules in the contractor role and guest role," is incorrect because the guest role (default 802.1X role) is not applied when a specific role is assigned via the Aruba-User-Role VSA.
The HPE Aruba Networking AOS-8 8.11 User Guide states:
"When a user authenticates successfully via 802.1X, the Mobility Controller applies the role specified in the Aruba-User-Role VSA returned by the RADIUS server in the Access-Accept message. If the role specified in the VSA exists on the controller, it is applied to the user session, overriding any default 802.1X role configured for the WLAN. The controller does not combine the VSA-specified role with other roles, such as the initial, logon, or default roles." (Page 305, Role Assignment Section)
Additionally, the HPE Aruba Networking ClearPass Policy Manager 6.11 User Guide notes:
"ClearPass can send the Aruba-User-Role VSA in a RADIUS Access-Accept message to assign a specific role to the user on Aruba Mobility Controllers. The role specified in the VSA takes precedence over any default roles configured on the WLAN, ensuring that the user is placed in the intended role." (Page 289, RADIUS Enforcement Section)
[References:, HPE Aruba Networking AOS-8 8.11 User Guide, Role Assignment Section, Page 305., HPE Aruba Networking ClearPass Policy Manager 6.11 User Guide, RADIUS Enforcement Section, Page 289.===========]
