Aruba ClearPass icon

Aruba ClearPass

Interact with Aruba ClearPass API

Local Users → Update

AI-generated

Overview

This node interacts with the Aruba ClearPass API to update local user accounts within the 'Identities' domain. It is useful for scenarios where you need to modify existing local user details such as enabling or disabling the account, changing the password, updating the username, or modifying user roles. For example, an administrator can use this node to update a user's password or change their role in the system programmatically.

Use Case Examples

  1. Updating a local user's password and role after a security policy change.
  2. Disabling a local user account when the user leaves the organization.

Properties

Name Meaning
Domain API domain to access, fixed to 'Identities' for local user operations.
Local User ID Numeric ID of the local user to update.
Update Fields Fields to update for the local user, such as user ID, password, username, and role name.
Additional Fields Additional optional fields for the local user, including account enabled status, password change requirement on next login, and custom attributes as key/value pairs.

Output

JSON

  • id - The unique identifier of the updated local user.
  • user_id - The unique user ID of the updated local user.
  • username - The username of the updated local user.
  • role_name - The role name assigned to the updated local user.
  • enabled - Boolean flag indicating if the user account is enabled.
  • change_pwd_next_login - Boolean flag indicating if the user must change password on next login.
  • attributes - Additional attributes stored with the local user account as key/value pairs.

Dependencies

  • Aruba ClearPass API access with appropriate credentials

Troubleshooting

  • Common issues include invalid or missing Local User ID, insufficient permissions to update user details, or incorrect API domain selection.
  • Error messages may indicate authentication failures, invalid input data, or network connectivity problems.
  • Ensure the API credentials are correctly configured and the Local User ID exists before attempting an update.

Links

Discussion