Aruba ClearPass

Interact with Aruba ClearPass API

Overview

This node integrates with the Aruba ClearPass API, allowing users to manage various resources within specified API domains such as "Identities," "Policy Elements," and "Enforcement Profile." Specifically, for the Endpoints resource under the Identities domain, it supports operations including deleting an endpoint by its numeric ID.

A common use case is automating network security management tasks, such as removing obsolete or unauthorized endpoints from the ClearPass system. For example, when a device leaves a network, this node can be used in a workflow to delete its corresponding endpoint record automatically, helping maintain an up-to-date inventory of network devices.

Properties

Name Meaning
Domain The API domain to access. Options: "Identities", "Policy Elements", "Enforcement Profile".
Endpoint ID Numeric ID of the endpoint to delete. Required when Domain is "Identities" and Resource is "Endpoint".

Output

The node outputs an array of JSON objects representing the result of the executed operation. For the Delete operation on Endpoints, the output typically contains confirmation of deletion or relevant status information returned by the ClearPass API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Aruba ClearPass API.
  • The node depends on an internal helper module (executeOperation) that handles the actual API request execution.
  • Proper configuration of the API credentials in n8n is necessary for successful communication.

Troubleshooting

  • Common Issues:

    • Invalid or missing Endpoint ID will cause the delete operation to fail.
    • Incorrect API credentials or insufficient permissions may result in authentication errors.
    • Network connectivity issues can prevent the node from reaching the ClearPass API.
  • Error Messages:

    • Errors thrown during execution are logged and, if "Continue on Fail" is enabled, returned as part of the node's output.
    • Typical error messages include authentication failures, invalid resource identifiers, or API rate limits.
  • Resolution Tips:

    • Verify that the Endpoint ID is correct and exists in the ClearPass system.
    • Ensure the API key credential is valid and has appropriate permissions.
    • Check network connectivity and firewall settings.
    • Enable "Continue on Fail" to handle errors gracefully in workflows.

Links and References

Discussion