<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
Explanation of System Log SMS Events When SMS Authentication Is Disabled
Okta Classic Engine
Okta Identity Engine
Okta Verify
Overview

This article explains why the event system.sms.send_okta_push_verify_message appears in the system logs even when Short Message Service (SMS) authentication is not in use. It describes the specific user enrollment actions that trigger this event and how to modify the configuration to prevent these messages.

Applies To
  • Okta Verify
  • System Logs
  • Authenticators
  • Okta Classic Engine
  • Okta Identity Engine (OIE)
  • Short Message Service (SMS)
Cause

The event occurs when a user enrolls in Okta Verify and selects Can't scan? and then Text me a setup link during the enrollment process. Okta sends an SMS containing a download link for the Okta Verify application. This message is generated by the Okta Verify enrollment process, not the SMS Authenticator.

Solution

To prevent these messages and block the SMS setup option for users, perform the following steps:

  1. Navigate to Security > Authenticators.
  2. Locate Okta Verify and select Edit.
  3. Disable the Any method option that allows sending setup links via SMS.
  4. Navigate to Security > Authenticators > Enrollment.
  5. Ensure the Phone Authenticator remains disabled to prevent SMS-based authentication.

This configuration ensures users can enroll in Okta Verify only via higher-security methods, eliminating SMS-based setup links.

Enrollment options

Loading
Explanation of System Log SMS Events When SMS Authentication Is Disabled