Zitadel

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. It allows users to call various services offered by Zitadel, such as user management, organization management, authentication, administration, and more.

Specifically, the startIdentityProviderIntent operation under the "UserService" resource initiates an identity provider intent, which is typically used in scenarios where you want to start or trigger an identity provider flow (e.g., SSO login, linking external identity providers).

Practical examples:

• Starting an identity provider login flow for a user.
• Initiating a connection to an external identity provider using specific URLs and LDAP configuration.
• Automating identity provider intents as part of a larger workflow involving user authentication or provisioning.

Properties

Output

The output JSON contains the raw response from the Zitadel API corresponding to the invoked operation. For startIdentityProviderIntent, this will include data returned by the Zitadel UserService's method, likely containing information about the initiated identity provider intent such as status, tokens, or redirect URLs.

No binary data output is indicated by the code.

Example output structure (simplified):

{
  // Response fields depend on Zitadel API's startIdentityProviderIntent response
}

Dependencies

• Requires an API key credential for Zitadel (referred generically as an API token).
• Uses the nice-grpc library to communicate with Zitadel gRPC services.
• The node expects the Zitadel API endpoint URL hardcoded as https://zitadel.studentcouncil.dk.
• The node dynamically loads service definitions from bundled generated Zitadel protobuf clients.

Troubleshooting

• Invalid or missing API token: If the API token is not set or invalid, requests will fail authorization. Ensure the API key credential is configured correctly.
• Incorrect property values: The properties idpId, urls, and ldap must be valid strings; malformed JSON or incorrect formats may cause errors.
• Operation not found: If an unsupported operation is selected, the node returns empty JSON without error but no action is performed.
• Parsing errors: The node attempts to parse input parameters as JSON; if parsing fails, it falls back to using the raw string. Ensure inputs are properly formatted.
• Network issues: Connectivity problems to the Zitadel API endpoint will cause request failures.

Links and References

• Zitadel Official Website
• Zitadel API Documentation
• gRPC Node.js Library

If you need further details on other operations or resources, please provide their names.