Okta Telephony Inline Hook

Overview

Okta’s telephony inline hook lets you bring your own SMS or voice provider for authentication flows. With EZITXT, you can connect Okta to your messaging service so Okta can send one-time passcodes and recovery messages through your existing account.

This integration is typically used for:

• SMS-based multi-factor authentication
• Phone number enrolment
• Account unlock via SMS
• Password reset via SMS

Okta provides the policy and user flow configuration, while EZITXT provides the telephony delivery channel.

For background on Okta’s bring-your-own-telephony requirement, see Okta’s support article: Bring your own telephony required for SMS and voice.

Before You Begin

Before setting up the integration, make sure you have:

• An Okta administrator account
• Access to
• Permission to open Integrations > API Configuration in
• A secure place to store credentials while configuring Okta

If you do not see Okta Inline Hook in the platform, contact support@ezitxt.com before starting the Okta setup.

Retrieve Setup Details

To get the values you need for Okta:

1. Sign in to .
2. Go to Integrations > API Configuration.
3. Select Okta Inline Hook.
4. Note the following values shown in the application:
   • Application Name
   • Authentication Details
   • Okta Setup Values
5. If you do not already have an authentication secret, select Generate New Password.

Under Okta Setup Values, take note of these values as they will need to be entered into the Okta setup page. See Create the Telephony Inline Hook in Okta for where to enter them.

• URL
• Authentication Field
• Authentication Secret

Create the Telephony Inline Hook in Okta

1. Sign in to the Okta Admin Console with an administrator account.
2. Go to Workflow > Inline Hooks.
3. Select Add Telephony Inline Hook.
4. Choose Telephony as the hook type.

On the Create Inline Hook page, enter the following values:

• Name: Any descriptive name, for example EZITXT SMS Provider
• Authentication type: HTTP headers

Use the URL, Authentication Field, and Authentication Secret values from the platform.

Select Save to create the inline hook.

Configure SMS Use Cases in Okta

After the inline hook is connected, you can configure Okta to use SMS for:

• Second-factor authentication
• Phone enrolment
• Account unlock
• Password reset

The remaining Okta-side setup depends on your sign-in policies, authenticators, and recovery settings. Follow Okta’s guide to complete that configuration:

• Okta telephony configuration tasks

Troubleshooting

If the integration does not work as expected, check the following:

Configuration Checks

• Confirm the hook URL is correct
• Confirm HTTP headers is selected as the authentication type
• Confirm the Authentication Field and Authentication Secret exactly match the values shown in the platform
• If you generated a new password in the platform, confirm the updated secret was copied into Okta

Okta Checks

• Confirm the inline hook is saved and active
• Confirm SMS is enabled in the relevant Okta authentication and recovery flows
• Review Okta system logs for telephony-related errors: Getting started with Okta system logs

Platform Checks

• Sign in to the platform and open Mobile Report
• Search for the affected authentication message
• Confirm whether the message was submitted and check the delivery status

Common Causes

• The user’s phone number is incorrectly formatted in Okta
• The authentication secret was copied incorrectly
• The platform password was rotated but not updated in Okta
• The receiving handset or carrier is blocking SMS delivery

If you still need help, contact support@ezitxt.com.

Security Notes

• Treat the authentication secret as a sensitive credential
• Only share the authentication secret with authorised administrators
• If you suspect the secret has been exposed, generate a new password in the platform and update the Okta inline hook immediately
• All communication between Okta and EZITXT is secured over HTTPS