Verify TOTP is in Public Beta.
Want to see this in action first? Check out Twilio's Code Exchange and quick deploy a sample TOTP application.
Verify TOTP adds the standards-compliant TOTP (Soft Token) channel to the Verify API, so that you can let your users use authenticator apps like Authy, Google Authenticator, or your own custom app for authentication. It’s great for businesses looking for a more secure, private, and lower-cost user authentication option compared to SMS OTP. TOTP even works when the user is offline, like on an airplane. Unlike the existing Authy API TOTP feature, no PII from the user is required, more user registration options beyond QR codes are supported, and you can configure more code properties.
There are three main steps to use Verify TOTP:
- Register a user by generating an RFC-6238 compliant seed.
- Verify that the user correctly added the seed (for example via QR code) to their Authenticator App
- To verify a registered user, check that the code a user provided matches the code generated by the unique seed.
This Quickstart will walk you through the entire process step-by-step, starting with setting up your Twilio account all the way through verifying a user.
- Create a Verify Service
- Generate a TOTP seed
- Generate a QR code
- Verify a successful registration
- Create a Challenge
- Update the Challenge
By the end of this Quickstart, you’ll have a solid foundation for implementing Verify TOTP within your app and backend to verify users at login, transaction, and other sensitive actions.
Want a technical overview first?Technical Overview
Check out the Verify TOTP Technical Overview to view its data model and sequence diagrams
Already have a Twilio account? Go ahead and skip this section.
You can sign up for a free Twilio trial account here.
- When you sign up, you'll be asked to verify your personal phone number. This helps Twilio verify your identity.
- Once you verify your number, you'll be asked to create a project. For the sake of this tutorial, you can click on the "Learn and Explore" template. Give your project a name, or just click "skip remaining steps" to continue with the default.
- Once you get through the project creation flow, you'll arrive at your project dashboard in the Twilio Console. This is where you'll be able to access your Account SID, an authentication token, create a Verify Service and more.
Go to Twilio Console > Verify > Services and create a new Service:
Alternatively, you can select any existing Service. However, we recommend creating a new service for testing so you don't accidentally interfere with a production environment.
To use Verify TOTP, you first register a user by generating an RFC-6238 compliant seed. Then you verify that they've correctly added it to their Authenticator App for generating codes.
The security of TOTP relies on a shared secret between your app and your user, and this is known as the seed. Register a user by creating a TOTP factor, which generates a seed based on a set of default configs and stores it. A corresponding Entity representing your user is also auto-created if it didn’t exist.
When creating a TOTP factor, you can optionally pass your own seed (useful for migration scenarios) and modify the default configs. See the Factor resource for reference. Some default configs are also adjustable at the Service resource level, such that all future Factors use them. Type or paste the code sample for this step.
Do not use Personally Identifiable Information for
identity. Use an immutable user identifier like a UUID, GUID, or SID.
Verify TOTP uses
identity as a unique identifier of a user. You should not use directly identifying information (aka personally identifiable information or PII) like a person's name, home address, email or phone number, etc., as
identity because the systems that will process this attribute assume it is not directly identifying information.
Use caution when changing default configs
The default configs for the TOTP code (Config.CodeLength, Config.Skew, Config.TimeStep, and Config.Alg) have been chosen for a typical TOTP use case with a 6-digit length code. Please use caution when changing these configs, as it could reduce the security of the code. For example, reducing the length of the TOTP code (Config.CodeLength) makes the code easier to guess and more vulnerable to a brute force attack. While a shorter length may be necessary for your use case, consider compensating security enhancements, such as limiting the rate at which codes can be checked, reducing Config.Skew, and reducing Config.TimeStep. Another factor to consider is that publicly available authenticator apps that your users might have don't support non-default configs for all mobile OSs; see this 3rd-party analysis of authenticator apps for details. Contact Twilio for further guidance.
The user needs to add the seed, and optionally metadata like Issuer and Account Name, to an authenticator app like Google Authenticator, Twilio Authy, or a custom client app that you’ve provided to your user. This authenticator app needs to securely store the seed and generate TOTP codes using it. A typical way for the user to add the seed is via scanning a QR code. Verify TOTP generates a standard URI (factor.binding.uri) that you can convert into a QR code for this purpose. Verify TOTP does not generate the QR code itself, but there are many free/open-source QR code generators.
For this quickstart, use qr-code-generator.com to quickly generate a QR code by pasting the URI.
For a real implementation, you could use one of these open-source code libraries:
- Node: https://github.com/soldair/node-qrcode or https://www.npmjs.com/package/otplib
- Go: https://github.com/skip2/go-qrcode
- Python: https://pypi.org/project/PyQRCode/
- PHP: https://github.com/endroid/qr-code
Scan and add this QR with your favorite authenticator app to mimic what a user would do.
Using this URI:
Generates this QR code using qr-code-generator.com:
Scanning this QR using the Twilio Authy app generates this token:
Instead of a QR code, you can pass the seed to the user’s authenticator app by displaying it for manual entry by the user (supported by most commercial authenticator apps), including it in a deep link, or sending it via another authenticated channel.
When the Factor is first created, it's in an “unverified” status. To verify the Factor, the user needs to demonstrate that they are able to generate a correct code based off of the seed.
Use the code generated by your authenticator app and type or paste the code sample for this step.
Be sure to update the AuthPayload value with your latest TOTP code before sending the API request. The expiration window (Config.TimeStep) of the TOTP code defaults to 30 seconds. If the TOTP code is correct, then the Factor status will change to "verified". If it's incorrect, the Factor status will remain "unverified."
The Factor SID (
YFXXX..) is included in the response when you create a Factor. If you don't have the Factor SID, you can List Factors for your user’s Entity, and identify the one that is factor_type = totp.
Congratulations! You've just completed the first Verify TOTP sequence: register user and TOTP seed. The second sequence is to verify (authenticate) a user with their authenticator app, whenever they need to login to your app or perform some other sensitive action. Read on for the step-by-step instructions.
To verify a user, the user needs to read the latest code generated by their authenticator app and provide it to you. Then you need to create a Challenge and include the code as the
AuthPayload. If the code is correct, then the Challenge will be created with a status of
approved. Incorrect codes will result in a Challenge that is created with a status of
pending, and will eventually expire. In the event of an incorrect code, you can ask the user to provide a new code and create a new Challenge to check if it's correct. Alternatively, you can update the existing Challenge with a new
AuthPayload value, but this approach is probably more complicated to implement. Type or paste the code sample for this step.
Now that you've verified your first user, we’d love your feedback on your experience and whether you plan to use Verify TOTP in production. We’d be happy to discuss your plans and offer suggestions. In addition, explore adding Verify's other verification channels beyond TOTP.