Zitadel

Overview

This node integrates with the Zitadel API, allowing users to interact with various Zitadel services programmatically. Specifically, the listPasskeys operation under the "Default" resource (mapped here as a service-operation pair) fetches a list of passkeys associated with a user. This is useful in scenarios where you want to manage or audit user authentication methods, such as retrieving all registered security keys for a given user.

Practical examples include:

• Retrieving all passkeys for a user to display them in an admin dashboard.
• Auditing user authentication methods for compliance or security reviews.
• Automating user management workflows that involve passkey enumeration.

Properties

Output

The output JSON contains the raw response from the Zitadel API's listPasskeys method. This typically includes details about each passkey registered to the specified user, such as identifiers, creation dates, and possibly metadata related to the passkeys.

If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON-based.

Example output structure (simplified):

{
  "passkeys": [
    {
      "id": "string",
      "createdAt": "timestamp",
      "name": "string",
      "metadata": { /* additional passkey info */ }
    },
    ...
  ]
}

Dependencies

• Requires an API authentication token (Personal Access Token) for Zitadel, configured in the node credentials.
• Connects to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• Uses gRPC client libraries (nice-grpc) to communicate with Zitadel services.
• No other external dependencies are required.

Troubleshooting

• Authentication errors: If the node fails due to authorization issues, ensure the API token credential is correctly set up and has sufficient permissions.
• Invalid userId: Providing an incorrect or non-existent user ID will result in empty or error responses. Verify the user ID before running the node.
• JSON parsing errors: Input parameters like query fields are parsed as JSON; malformed JSON input can cause failures. Ensure proper JSON formatting if modifying advanced parameters.
• Operation not found: Selecting an unsupported operation for the chosen service will return an empty JSON object. Confirm the operation name matches the available methods for the selected service.

Links and References

• Zitadel API Documentation
• Zitadel GitHub Repository
• nice-grpc Library - used for gRPC communication in this node