ZitadelInstall

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. Specifically, the removeU2F operation under the "Default" resource (mapped here as part of the UserService) allows users to remove a U2F (Universal 2nd Factor) device from a user's account. This is useful in scenarios where a user wants to revoke or unregister a security key used for two-factor authentication.

Practical examples include:

• An administrator removing a lost or compromised U2F device from a user's profile.
• Automating cleanup of U2F devices when users leave an organization.
• Managing multi-factor authentication devices programmatically via workflows.

Properties

Output

The output JSON contains the response from the Zitadel API after attempting to remove the specified U2F device. The exact structure depends on the Zitadel API's response schema for the removeU2F method but generally includes confirmation of success or details about the removal operation.

No binary data output is produced by this node.

Example output JSON snippet:

{
  "result": {
    "details": "U2F device removed successfully",
    "userId": "user-id-value",
    "u2fId": "u2f-device-id"
  }
}

Dependencies

• Requires an API authentication token (Personal Access Token) for Zitadel, configured in n8n credentials.
• Connects to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• Uses gRPC client libraries internally to communicate with Zitadel services.

Troubleshooting

• Common issues:

  • Invalid or missing API token: Ensure the Zitadel API credential is correctly set up with a valid Personal Access Token.
  • Incorrect userId or u2fId: Verify that the IDs correspond to existing user and U2F device entries in Zitadel.
  • Network connectivity problems: Confirm that the n8n instance can reach the Zitadel API endpoint.

• Error messages:

  • Authorization errors typically indicate invalid or expired tokens; refresh or update credentials.
  • Not found errors suggest the specified user or U2F device does not exist; double-check input values.
  • Parsing errors may occur if input parameters are malformed JSON; ensure inputs are properly formatted strings.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• Universal 2nd Factor (U2F) Overview

This summary is based solely on static analysis of the provided source code and property definitions.