HPE Aruba Networking ClearPass Policy Manager - Update custom attributes on MAC addresses
HPE Aruba Networking ClearPass Policy Manager - Update custom attributes on MAC addresses sets a custom attribute value on the endpoint that matches each asset's MAC address in HPE Aruba Networking ClearPass Policy Manager. Optionally, it also creates or updates a role mapping policy that maps the attribute value to a ClearPass role. Use it to tag endpoints so that they receive a specific role, for example for network segmentation, for:
- Assets returned by the selected query or assets selected on the relevant asset page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
When accessing an enforcement action using the API, you must use the backend form of field names.
Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

Note
- Not all asset types are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Aggregated Security Findings.
- See Actions supported for Software.
Required Fields
These fields must be configured to run the Enforcement Action.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
-
Use stored credentials from the HPE Aruba Networking ClearPass Policy Manager adapter - Select this option to use credentials from an existing ClearPass adapter connection. By default, the first connection is selected.
-
When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
Note
To use this option, you must successfully configure an Aruba ClearPass adapter connection.
-
-
NAC Custom Attribute Name - Enter the name of the Endpoint custom attribute in ClearPass (default:
axonius_ew_seg_id). Axonius creates the attribute if it does not exist. -
Attribute Value to Assign - Enter the segment value to write to the custom attribute of every selected endpoint.
-
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.
Note
Axonius uses the first MAC address in the ClearPass adapter data of each asset. Assets without a MAC address in ClearPass adapter data fail with the status No MAC address found on the ClearPass adapter data. If a MAC address does not match a ClearPass endpoint, the action fails for that asset with a "not found" status.
Additional Fields
These fields are optional.
- Aruba Role Name - Enter the name of a ClearPass role. When set, Axonius creates or updates a role mapping policy that assigns this role to endpoints whose custom attribute equals the Attribute Value to Assign.
- Role Mapping Policy Name - Enter the name of the role mapping policy. If empty, Axonius uses
Axonius EW Segment - <role name>. - Role Mapping Default Role Name - Enter the default role of the role mapping policy (default:
[Other]).
Connection Settings
Connection and CredentialsWhen Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.
- Aruba ClearPass Domain - The hostname or IP address of the ClearPass server that Axonius can communicate with via the Required Ports.
- Client ID - The Client ID of the ClearPass API client.
- Client Secret - The Client Secret of the ClearPass API client.
Verify SSL (Optional) (default: enabled) - Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings. This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting.)
HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
Gateway Name - Select the Gateway through which to connect to perform the action.
APIs
Axonius uses the Aruba ClearPass REST API:
- POST
/api/oauth- Authenticates with the client credentials grant. - POST
/api/attribute- Creates the Endpoint custom attribute. Axonius treats an attribute that already exists as success. - GET
/api/role-mapping/name/{name}- Checks whether the role mapping policy exists. Used only when Aruba Role Name is set. - POST
/api/role-mapping- Creates the role mapping policy if it does not exist. Used only when Aruba Role Name is set. - PUT
/api/role-mapping/{role_mapping_id}- Updates the role mapping policy if it exists. Used only when Aruba Role Name is set. - PATCH
/api/endpoint/mac-address/{mac_address}- Sets the custom attribute on the endpoint.
Required Ports
Axonius must be able to communicate via the following ports:
- TCP port 443 (HTTPS), or the port specified in the ClearPass domain you configure.
Required Permissions
The stored credentials, or those provided in Connection and Credentials, must have the necessary permissions to perform this enforcement action.
The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:
The following permissions and requirements are needed:
- A ClearPass API client with the Client Credentials grant type, and the Axonius IP address in the ClearPass API access list. For details, see Aruba ClearPass.
- An operator profile for the API client that includes API Services access and permission to modify endpoints and their attributes. [To Verify] When you set Aruba Role Name, the profile must also allow creating and updating role mappings. The read-only permissions used to fetch data are not enough for this action.
To learn more about Enforcement Actions, see Enforcement Actions.
Version Matrix
This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.
| Version | Supported | Notes |
|---|---|---|
| ClearPass Policy Manager [To Verify] | [To Verify] | Uses the ClearPass REST API (/api). |
For more details about other enforcement actions available, see Action Library.
Updated about 2 hours ago
