<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

Rockstar Extension Displays a "There Is No Verified Phone Number on File" Error in Okta

Okta Classic Engine
Okta Identity Engine
Multi-Factor Authentication

Overview

A missing verified phone number associated with a call factor causes an error when verifying the factor using the Rockstar browser extension. Resolve this issue by re-enrolling the phone number via the Okta application programming interface (API) and deleting the factor to reset the enrollment state. When attempting to verify a factor using the Rockstar browser extension, Okta generates the following error:

 

There is no verified phone number on file

 

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • Rockstar
  • Okta Application Programming Interface (API)

Solution

How is the missing verified phone number error resolved?

Re-enroll the previously used phone number and remove the call factor using the Okta API by executing a POST request to re-enroll the factor and a DELETE request to reset the enrollment state.

  1. Re-enroll the factor by making a POST request to the following endpoint using the previously known phone number for the affected user: POST <url>/api/v1/users/<userId>/factors.
  2. Locate the factor id in the successful response.
  3. Remove the call factor by making a DELETE request to the Reset Factor endpoint using the factor id and the removeRecoveryEnrollment=true parameter: DELETE <url>/api/v1/users/<userId>/factors/<factorId>?removeRecoveryEnrollment=true.
  4. Verify the removal of the call factor and ensure the user can successfully authenticate or re-enroll in the required factors.
Loading
Rockstar Extension Displays a "There Is No Verified Phone Number on File" Error in Okta | Okta Support