<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language

Users are Able to Use Okta Verify Push despite Them Not Being Allowed by the Sign-on Policies

Okta Identity Engine
Multi-Factor Authentication

Overview

This document covers a situation where users have the possibility to use Okta Verify Push despite the enrollment policy allowing the use of Phishing Resistant authenticators. 

Applies To

  • Phishing Resistant
  • Okta Verify
  • Okta Identity Engine (OIE)
  • Upgrade

Cause

Some users that were enrolled into Okta Verify Push prior to the OIE upgrade, have the option to use it to validate sign-on even when using new, phishing resistant authentication policies.

Solution

Resetting Okta Verify for the user from the Admin Dashboard should fix it. However, if the behavior can be replicated with the user after the reset, then please contact Okta Support. 

Loading
Users are Able to Use Okta Verify Push despite Them Not Being Allowed by the Sign-on Policies | Okta Support