<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

Verify If a User Is Using Okta Telephony Vendor or Telephony Inline Hook for SMS or Call Authentication

Okta Classic Engine
Multi-Factor Authentication
Okta Identity Engine

Overview

Administrators must verify whether an end user receives SMS or call authentication via an Okta telephony vendor (Twilio or Telesign) or a Telephony Inline Hook (Bring Your Own Telephony). Reviewing the Okta System Log provides the necessary provider details to confirm the telephony source. This verification ensures compliance with the Okta's BYOT policy..

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • Multi-Factor Authentication (MFA)
  • SMS / Voice / Phone

Solution

How is the telephony provider verified in the Okta System Log?

Navigate to the Okta System Log and search for specific authentication events to identify the telephony provider.

  1. Open the System Log and expand the logs under System.
  2. Locate the following event information for a call:
Send second factor auth call
SUCCESS
  1. Locate the following event information for an SMS:
Send second factor auth SMS
SUCCESS

 

The following queries identify the specific telephony provider used.

Execute the provided queries in the Okta System Log to determine if an Okta telephony vendor, a Telephony Inline Hook, or a custom telephony provider handled the authentication request.

If Okta Telephony Vendor was used for SMS / Call
SMSProvider Name
CallProvider Name

In this example, the Okta Telephony Provider "Telesign" was used for authentication.


Okta System Log Search:

  • debugContext.debugData.smsProvider eq "TELESIGN"
  • debugContext.debugData.smsProvider eq “TWILIO”

 

 

If the Telephony Inline Hook was used for SMS / Call via Workflows > Inline Hooks > Telephony
SMSProvider Name
CallProvider Name

In this example, the Telephony Inline Hook "Twilio" was used for authentication.


Okta System Log Search:

  • debugContext.debugData.smsProvider eq "TELEPHONY_PROVIDER_HOOK"

 

 

If BYOT or Telephony Provider was used for SMS / Call via Customizations > Telephony Providers
System log
System log

Okta System Log Search:

  • debugContext.debugData.smsProvider eq "CUSTOM_TWILIO"

Related References

Loading
Okta Support - Verify If a User Is Using Okta Telephony Vendor or Telephony Inline Hook for SMS or Call Authentication