Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a user management system to delete a specific access token associated with a user. It is useful in scenarios where you need to revoke or invalidate an existing access token for a user, such as when a token is compromised, expired, or no longer needed. For example, an administrator can use this node to remove a user's API token to prevent further access without deleting the entire user account.

Properties

Name Meaning
Username The username of the user whose access token you want to delete.
Token The identifier of the token to be deleted; it can be specified by its ID or name.

Output

The node outputs JSON data representing the result of the token deletion operation. Typically, this will confirm whether the token was successfully deleted or provide error information if the deletion failed. There is no indication that the node outputs binary data.

Dependencies

  • Requires an API key or authentication token credential to connect securely to the user management system.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the external user management API to perform token deletion.

Troubleshooting

  • Common issues:

    • Providing an incorrect username or token identifier may cause the deletion to fail.
    • Insufficient permissions or invalid API credentials can lead to authorization errors.
    • Network connectivity problems can prevent the node from reaching the API endpoint.
  • Error messages and resolutions:

    • "Token not found": Verify that the token ID or name is correct and belongs to the specified user.
    • "Unauthorized" or "Authentication failed": Check that the API credentials are valid and have sufficient rights.
    • "Network error" or "Timeout": Ensure the API server is reachable and there are no firewall restrictions.

Links and References

  • Refer to your user management system's API documentation for details on token management endpoints.
  • Consult n8n documentation on setting up API credentials and handling HTTP request nodes for similar integrations.

Discussion