Okta Custom Telephony Provider Feature Not Working as Expected When Using Factors API Verify Endpoint
Last Updated:
Overview
When attempting to verify a factor using the /api/v1/users/<userId>/factors/<factorId>/verify Application Programming Interface (API) endpoint, Okta sends Short Message Service (SMS) messages from the default Okta telephony provider instead of the configured custom telephony provider. This occurs even when the Bring Your Own Carrier (BYOC) Early Access (EA) feature is enabled and active. This issue happens because the BYOC EA feature does not currently support Classic flows, and the factors API uses a Classic endpoint.
Applies To
- Okta Identity Engine (OIE)
- Bring Your Own Carrier (BYOC) Early Access (EA)
- Short Message Service (SMS) Factor
- Call Factor
- Application Programming Interface (API)
- Custom Telephony Provider
Cause
The BYOC EA feature does not currently support Classic flows. The factors API uses a Classic endpoint. Therefore, even if the environment is on OIE, sending an SMS message via a Classic endpoint utilizes the default Okta telephony providers regardless of the custom provider configuration.
Solution
Why does the custom telephony provider feature fail with the factors API?
Currently, there is no workaround to force the factors API to use the custom telephony provider. Support for telephony custom credentials in the Okta Classic Engine is planned for a future General Availability (GA) release, which will resolve the API endpoint issue.
