Actions42
- getUserByID
- addHumanUser
- listUsers
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- registerTOTP
- verifyTOTPRegistration
- removeTOTP
- addOTPSMS
- removeOTPSMS
- addOTPEmail
- removeOTPEmail
- startIdentityProviderIntent
- retrieveIdentityProviderIntent
- addIDPLink
- listIDPLinks
- removeIDPLink
- passwordReset
- setPassword
- listAuthenticationMethodTypes
- createInviteCode
- resendInviteCode
- verifyInviteCode
Overview
This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, for the registerU2F operation under the default resource, it facilitates registering a U2F (Universal 2nd Factor) device for a user. This is useful in scenarios where enhanced security via two-factor authentication is required.
Practical examples include:
- Registering a new U2F security key for a user in an identity management system.
- Automating multi-factor authentication setup workflows within an organization.
- Managing user security settings programmatically through the Zitadel platform.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, "UserService" is relevant. |
| userId | The unique identifier of the user for whom the U2F device will be registered. |
| domain | The domain context under which the U2F registration is performed. |
Output
The node outputs a JSON object containing the response from the Zitadel API's registerU2F method. This typically includes details about the U2F registration process such as challenge data or confirmation of successful registration.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
- 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 authentication token can cause authorization failures.
- Incorrect
userIdordomainvalues may result in errors or empty responses. - Network connectivity problems to the Zitadel API endpoint.
Error messages and resolutions:
- Authorization errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Validation errors on input parameters: Verify that
userIdanddomainare correctly specified and conform to expected formats. - Timeout or connection errors: Check network access to the Zitadel API URL and retry.