EdwardB.18998 (Customer) asked a question.
I'm using a recently created instance of Identity Engine for local testing. I'm otherwise working with / part of the MassHousing tenant.
The older version of OKTA did not require setting up a third party telephony provider ("Inline Hook"), but the new one does.
A couple of questions:
1) Is there any way to do local testing of SMS/Phone locally with Identity Engine without having to sign up with a third party provider such as Twilio?
2) Our Test environment has been upgraded to use Identity Engine, but apparently was grandfathered to use OKTA's default SMS/Phone provider, as it still works. Is there a sunset date for that grandfathering? We intend to go to the Identity Engine in Production and need to know what to expect.
I appreciate in advance anything else you can add for what we can expect from this change.
https://sec.okta.com/articles/2023/08/byo-telephony-and-future-sms-okta
As of this month, any new Okta customer choosing to authenticate users (via the Workforce Identity Cloud) via SMS or voice will need to configure their own Telephony provider, just as they would any other custom IdP or custom TOTP factor.
In order to minimize disruption to existing services, Okta doesn’t intend to deprecate SMS for existing Workforce customers. Nonetheless, Okta Security urges existing workforce customers to accelerate their transition to passwordless with phishing-resistant factors like FastPass or FIDO2 WebAuthn.