--- title: "Default time-based OTP provider" slug: "default-time-based-otp-provider-v7-0" description: "Set up OTP authentication easily with our guide on using time-based authenticator apps, ensuring secure access to protected resources." tags: ["Time-Based OTP", "MFA", "MFA providers", "Multifactor Authentication"] updated: 2026-06-05T19:17:40Z published: 2026-06-05T19:17:40Z canonical: "support.appgate.com/default-time-based-otp-provider-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Default time-based OTP provider The built-in OTP provider works with most OATH time-based authenticator apps. The first time the app is needed, setup on the user’s mobile device starts automatically. The user is guided through download and setup, including seeding by QR code or manual entry. --- ## Initialization OTP authentication requires the app and server to share a secret called a seed. In AppGate ZTNA, a unique seed is created for the authenticator app during initialization: 1. The first time the user triggers an OTP user interaction that requires the default time-based OTP provider (or signs in to the admin UI), the user is prompted to set up an authenticator app. 2. The client displays a link. Selecting it opens another prompt with instructions for downloading and initializing the app. 3. After the seed is generated for the user's device, the admin UI updates to show that an OTP seed was created for that user device, but its status is flagged as *Unverified*. After the user enters a valid OTP to confirm the app is installed, the Controller removes the *Unverified* flag. 4. To view OTP seed status, go to the [Default Time-Based OTP Provider Seeds](/v1/docs/default-time-based-otp-provider-v7-0#default-timebased-otp-provider-seeds) page (Usage > Default Time-Based OTP Provider Seeds). 5. After initialization completes successfully, the user is prompted to enter a valid OTP. 6. After the user enters a valid OTP, the condition status updates the claims token, and the OTP seed status becomes verified. ### Initialization failure If initialization fails, the user can restart the OTP setup process: - Sign out of the client, sign back in, and then attempt to access the protected resource again. - This triggers the client to restart the OTP authenticator setup process. - The user is prompted again to download and set up the app, and the OTP seed is regenerated so the app can initialize correctly. ### Reseeding In other cases, the OTP app may need to be reinitialized, such as if the user gets a new mobile phone. To reseed: - Go to the **Default Time-Based OTP Provider Seeds** page. - Select the Action button (![Three circular shapes stacked vertically on a dark background, selected to access a menu.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/three_dots.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=L6mdPJCnTzMDOixg1D%2BITdtgdg8sD9%2FDRe4hGOi22x4%3D)) next to the user's OTP seed and select *Remove Seed*. - When the user tries to access the protected resource again, the OTP initialization process is started again --- ## The Default Time-Based OTP Provider Seeds page The **Default Time-Based OTP Provider Seeds** page (Usage > Default Time-Based OTP Provider Seeds) lists all users who have started installing and setting up a time-based, one-time password (OTP) app on a mobile device. The page shows the user’s *Username*, *Status*, and *Identity Provider*. Status can be one of the following: - ***Not Verified***. Client devices started initialization but have not yet verified completion. - ***Verified***. Client devices successfully initialized and seeded the authenticator app. The Controller and client manage OTP app deployment automatically. The client provides links and instructions and displays a QR code to seed the app. The Controller recognizes that the app is installed and seeded when the user enters a valid OTP. Until then, setup is treated as incomplete, and the seed is marked as *Not Verified*. --- ## Managing OTP providers Use the action button—the three dots icon (![Three circular shapes stacked vertically on a dark background, selected to access a menu.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/three_dots.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=L6mdPJCnTzMDOixg1D%2BITdtgdg8sD9%2FDRe4hGOi22x4%3D)) to the right of each line item—to access the following option: - ***Remove Seed***. Removes the OTP seed. Removing the seed restarts the OTP initialization process on the user's device. After the seed is deleted, initialization is triggered when the user attempts to access the protected resource.