Okta SMS Verification Message Is Sent Instead of Custom Telephony Provider

Okta sends the default SMS verification message instead of the custom message when an environment has a custom telephony provider configuration because the application uses the Classic Authentication API. Upgrading the application to use the Okta Identity Engine (OIE) authentication API resolves this issue. The Okta Admin Console contains a custom Twilio or Telesign account under Customizations and Telephony, but Okta sends the default SMS messages instead of the custom configured messages.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Custom Telephony (Twilio, Telesign)
• Classic Authentication API
• Remote Authentication Dial-In User Service (RADIUS)

Mobile applications, including RADIUS applications, that utilize the Classic Authentication API (/api/v1/authn) do not support custom telephony providers.

How does an API upgrade resolve the custom telephony provider issue?

Applications that utilize the Classic Authentication API (/api/v1/authn) require an upgrade to use the OIE authentication API (/primary-authenticate). Review the developer documentation to upgrade the application to use the OIE authentication API.

• Primary Authenticate API