Zitadel

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. It supports multiple services such as UserService, ManagementService, AuthService, and others, allowing users to perform various operations on these services.

The lockUser operation under the "Default" resource is designed to lock a user account, preventing that user from accessing the system. This can be useful in scenarios such as security enforcement, compliance, or administrative control when a user needs to be temporarily or permanently disabled.

Practical examples include:

• Locking a user after suspicious activity is detected.
• Temporarily disabling a user during an investigation.
• Enforcing organizational policies by locking inactive or terminated users.

Properties

Note: The property userId is used specifically with the UserService, while id is used with the ManagementService for the same operation.

Output

The output JSON contains the response from the Zitadel API corresponding to the lockUser operation. This typically includes details about the locked user or confirmation of the lock action.

Example structure (simplified):

{
  "json": {
    // Response object from Zitadel's lockUser method
  }
}

No binary data output is indicated by the source code.

Dependencies

• Requires an API authentication token (Personal Access Token) for Zitadel, provided via node credentials.
• Uses gRPC clients generated from Zitadel protobuf definitions to communicate with Zitadel services.
• The base URL for the Zitadel API is set to https://zitadel.studentcouncil.dk.
• The node depends on the nice-grpc library for gRPC communication.

Troubleshooting

• Invalid or missing API token: If the Personal Access Token is invalid or missing, the node will fail to authenticate. Ensure the correct token is configured in the node credentials.
• Incorrect user ID: Providing an incorrect or non-existent userId or id will result in errors from the Zitadel API. Verify the user identifiers before running the node.
• Operation not supported by service: Selecting an operation that does not exist for the chosen service will cause the node to return empty results or errors. Confirm the compatibility of service and operation.
• JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON strings will cause parsing failures. Provide valid JSON or plain strings as required.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• nice-grpc GitHub Repository

This summary is based solely on static analysis of the provided source code and input properties.