Configure the Okta Verify authenticator

Okta Verify is an authenticator that allows users to confirm their identity when they sign in to their Okta account or access Okta-protected resources. Users can also set up Okta Verify as a third-party authenticator to access sites that require multifactor authentication, like GitHub, Facebook, or Google.

When you configure Okta Verify, users are prompted to download, install, and set up the app on their device. The user experience depends on which Okta Verify options that the admin enables, and how the admin has configured app sign-in policies.

• Supported platforms for Okta Verify
• For user documentation, see Okta Verify for users overview.
• To find out what data types Okta Verify collects, see Data collected by Okta Verify.
• Okta Verify doesn't work during OOBE (Out-of-Box experience) in Windows Autopilot. To enable Autopilot deployments, see Integrate Okta with Windows Autopilot.

Add Okta Verify as an authenticator

1. In the Admin Console, go to SecurityAuthenticators.

2. On the Setup tab, click Add Authenticator.
3. Click Add on the Okta Verify tile.
4. Review the information message that appears, and then click Add.
5. Configure Okta Verify options.

Enroll Okta Verify in an authentication enrollment policy

1. In the Admin Console, go to SecurityAuthenticators.

2. On the Enrollment tab, add a new or edit an existing authentication enrollment policy.
   • If you're adding a policy: Click Add a Policy.
   • If you're editing a policy: Select the policy that you want to edit, and then click Edit.
3. In Effective factors, set Okta Verify to Optional or Required.
4. Save your changes by clicking Create Policy or Update Policy, as applicable.
5. To add one or more rules to the policy, see Configure rules for authenticator enrollment policies
6. Configure Okta Verify options.

Configure Risk Scoring

Okta's Risk Scoring capability allows you to increase the level of security that guards sign-in attempts to your org. It uses a data-driven risk engine to determine whether a sign-in event is likely to represent malicious activity. For example, you might want Okta to prompt users for multifactor authentication if the sign-in is considered high risk. See Risk scoring.

Risk Scoring can also strengthen the security of the Number Challenge functionality. See Configure Okta Verify options.

Related topics

Configure Okta Verify options

Create an authenticator enrollment policy

Configure rules for authenticator enrollment policies