chore: renamed one time password to OTP (#11447)

# Which Problems Are Solved

naming consistency for TOTP/OTP

# How the Problems Are Solved


# Additional Changes


# Additional Context

- Closes #11299 
- Closes #11302 
- Closes #11304

---------

Co-authored-by: Marco A. <[email protected]>
Co-authored-by: Florian Forster <[email protected]>
Co-authored-by: Copilot <[email protected]>
This commit is contained in:
Wim Van Laer
2026-02-04 10:20:47 +01:00
committed by GitHub
co-authored by Marco A. Florian Forster Copilot
parent 61d4060df3
commit b99271755b
77 changed files with 1688 additions and 1728 deletions
@@ -13,8 +13,8 @@ It is highly recommended to use MFA or [Passkeys](./passkey) to make your user a
ZITADEL supports different Methods:
- Time-based one time password (TOTP), which are Authenticator apps like Google/Microsoft Authenticator, Authy, etc
- One-time password sent as SMS
- One-time password sent as E-Mail
- OTP sent as SMS
- OTP sent as Email
- Universal Second Factor (U2F), which is authentication with your device like Windows Hello, Apple FaceID, Fingerprint, FIDO2 keys, Yubikey, etc.
## TOTP Registration
@@ -29,7 +29,7 @@ ZITADEL supports different Methods:
### Start TOTP Registration
The user has selected to setup Time-based One-Time Password (TOTP).
The user has selected to setup TOTP.
To show the user the QR to register TOTP with his Authenticator App like Google/Microsoft Authenticator or Authy you have to start the registration on the ZITADEL API.
Generate the QR Code with the URI from the response.
For users that do not have a QR Code reader make sure to also show the secret, to enable manual configuration.
@@ -205,7 +205,7 @@ curl --request POST \
### Add OTP SMS to the user
Now that the user has a verified phone number you can enable SMS OTP on the user.
Now that the user has a verified phone number you can enable OTP SMS on the user.
More detailed information about the API: [Add OTP SMS for a user](/reference/api/user/zitadel.user.v2.UserService.AddOTPSMS)
@@ -170,7 +170,7 @@ The following example shows you how you could use the events search to find out
You have to include all the event types that tell you that a login attempt has failed.
In this case these are the following events:
- Password verification failed
- One-time password (OTP) check failed (Authenticator Apps like Authy, Google Authenticator, etc)
- OTP check failed (Authenticator Apps like Authy, Google Authenticator, etc)
- Universal Second Factor (U2F) check failed (FaceID, WindowsHello, FingerPrint, etc)
- Passkey check failed (FaceID, WindowsHello, FingerPrint, etc)
@@ -189,8 +189,8 @@ Second factors (2FA):
- Time-based One Time Password (TOTP), Authenticator Apps like Google/Microsoft Authenticator, Authy, etc.
- Universal Second Factor (U2F), e.g FaceID, WindowsHello, Fingerprint, Hardware tokens like Yubikey
- One Time Password with Email (Email OTP)
- One Time Password with SMS (SMS OTP)
- One Time Password with Email (OTP Email)
- One Time Password with SMS (OTP SMS)
Force a user to register and use a multifactor authentication, by checking the option "Force MFA".
Ensure that you have added the MFA methods you want to allow.