Zitadel

Overview

This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, the removeTOTP operation under the "Default" resource is designed to remove a user's Time-based One-Time Password (TOTP) configuration, effectively disabling two-factor authentication for that user.

Common scenarios where this node is beneficial include:

• Automating user management workflows where administrators need to reset or disable 2FA for users.
• Integrating with identity and access management systems to programmatically control user security settings.
• Supporting helpdesk operations where users request removal of TOTP due to lost devices or other issues.

Example use case:

• An admin triggers this node to remove TOTP for a specific user by providing their user ID, thereby disabling their two-factor authentication temporarily or permanently.

Properties

Output

The node outputs a JSON object representing the response from the Zitadel API after attempting to remove the TOTP for the specified user. The exact structure depends on the Zitadel API's response schema for the removeTOTP method but generally includes confirmation of success or details about any errors encountered.

No binary data output is produced by this operation.

Dependencies

• Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
• The node uses the Zitadel gRPC client libraries bundled within its dependencies.
• The base URL for the Zitadel API is set to https://zitadel.studentcouncil.dk.
• Proper permissions are required on the API token to perform user management operations such as removing TOTP.

Troubleshooting

• Common Issues:

  • Invalid or missing user ID: Ensure the userId property is correctly provided and corresponds to an existing user.
  • Insufficient permissions: The API token used must have rights to modify user authentication settings.
  • Network or connectivity problems: Verify that the node can reach the Zitadel API endpoint.

• Error Messages:

  • Authorization errors typically indicate invalid or expired API tokens; refresh or replace the token.
  • Validation errors may occur if the user ID does not exist or the request payload is malformed.
  • Unexpected errors might require checking Zitadel API status or reviewing logs for detailed diagnostics.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• Time-based One-Time Password (TOTP) Overview