Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node is designed to delete an agent credential mapping within a system that manages credentials. It allows users to specify which credential mapping to remove by providing the unique identifier of the mapping. This operation is useful in scenarios where credential associations need to be cleaned up or revoked, such as when an agent no longer requires access or when credentials are rotated for security reasons.

Practical examples include:

  • Removing outdated or compromised credential mappings from an agent.
  • Automating cleanup of credential assignments during user offboarding processes.
  • Managing credential lifecycle by programmatically deleting specific mappings.

Properties

Name Meaning
X USER ID The User Id header value used for authentication or identification in the API request.
Id The unique numeric identifier of the agent credential mapping to be deleted.

Output

The node outputs JSON data representing the result of the deletion operation. Typically, this would include confirmation of successful deletion or details about any errors encountered. The exact structure depends on the API response but generally confirms whether the specified credential mapping was removed.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • Proper permissions must be granted to the API key to allow deletion of credential mappings.
  • The X USER ID header must be provided to identify the user context for the operation.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure this property is correctly set.
  • Invalid or non-existent Id: Providing an incorrect mapping ID will result in failure to delete. Verify the ID corresponds to an existing credential mapping.
  • Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Check credential configuration.
  • Permission denied: The API key might lack sufficient rights to delete mappings. Confirm the API key has appropriate scopes or roles.
  • Network or API availability issues: Ensure the Connect Secure API endpoint is reachable and operational.

Links and References

Discussion