Complete overview and step-by-step guide available at Telephony Inline Hook
.A Node.js application written to receive Telephony Inline Hook requests from Okta, parse user profile information, and, if verified, send an OTP through SMS or Voice (Call).
At a high-level, the following workflow occurs:
- A user attempts to sign in to Okta. The Okta org has an authentication requirement of a Phone authenticator. The user selects Receive a code via SMS.
- Okta generates a One-Time Passcode (OTP).
- Okta looks up whether any telephony hooks are configured and active for the org.
- A Telephony Inline Hook is triggered and sends a request to the provider to have them deliver the OTP.
- The external service evaluates the request, if the request headers are valid, the Telephony provider(s) request is made.
- The provider-specific response code and transaction ID are mapped to generic response categories, for provider-independent processing.
- Note: Although you can have only one active Telephony Inline Hook in your org at a time, logic in the external web service can direct requests to different providers based on conditions that you specify. For example, you can send the request to different telephony providers based on the country where the request originates.