Actions34
- Devices Actions
- Endpoints Actions
- Guest Users Actions
- Local Users Actions
Overview
This node integrates with the Aruba ClearPass API, allowing users to interact programmatically with various ClearPass domains and resources. It is designed to facilitate automation and data retrieval or manipulation within ClearPass environments, commonly used for network access control and policy enforcement.
Typical use cases include:
- Managing identities such as devices, endpoints, guest users, and local users.
- Handling policy elements like roles, role mappings, and enforcement policies.
- Accessing enforcement profiles for network security configurations.
For example, a user might automate the retrieval of endpoint information to synchronize with an asset management system or update enforcement policies based on dynamic network conditions.
Properties
| Name | Meaning |
|---|---|
| Domain | The API domain to access. Options: "Identities", "Policy Elements", "Enforcement Profile" |
Output
The node outputs an array of JSON objects representing the results returned from the Aruba ClearPass API operation executed. Each item corresponds to a resource entity fetched or affected by the operation.
If an error occurs and "Continue on Fail" is enabled, the output will contain a single JSON object with an error field describing the failure message.
No binary data output is indicated in the code.
Dependencies
- Requires an API key credential for authenticating with the Aruba ClearPass API.
- Depends on an internal helper module (
./helpers/executeOperation) that performs the actual API call logic. - The node expects proper configuration of credentials and network access to the ClearPass API endpoint.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Network connectivity problems preventing access to the ClearPass API.
- Incorrect domain or resource selections leading to unsupported operations.
Error handling:
- Errors during execution are logged to the console.
- If "Continue on Fail" is enabled, errors are returned as part of the node's output instead of stopping the workflow.
- Users should verify credentials and parameter correctness if errors occur.
Links and References
- Aruba ClearPass official API documentation (refer to Aruba Networks website)
- n8n documentation on creating custom nodes and handling credentials