The Okta Identity Engine is a set of customizable building blocks for every identity experience, breaking apart pre-defined authentication, authorization and registration flows.
Customers can create dynamic, context-based user journeys, unlocking the ability to address an unlimited number of identity use cases with minimal custom code.
Use context about the user, device, app, network, and intent to inform the identity journey of any user, adapting that identity experience accordingly.
The Okta Identity Engine is made up of a sequence of individual Steps that can handle the entire user journey from registration to authentication to authorization.
You can customize the behavior of each Step with Components. Components give you the ability to evaluate policies, trigger Hooks, publish events, prompt the user for action, or direct to an external service. Customizations can vary depending on the use case and the context applied. This means you can configure Okta to skip Steps in the engine. And, you can choose different Steps to run and skip for any app or at any point in the experience, creating a variety of identity sequences.
Based on the customizations applied, Okta can take further actions within each Step to progress the user through their journey:
- Email magic link authentication
- Step up authentication
- Gather more information
- Identity verification or validation
- Custom branding
- Route to an external system
The ability to execute Hooks and publish events, give you the power to support infinite use cases while still leveraging the security guardrails of the Okta Identity Engine. Hooks add extensibility to the Okta Identity Engine, allowing you to add custom code to do modify inflight processes and notify external services. There are two types of Hooks:
Allow you to add custom logic to a Component
Allow you to kickoff downstream integrations based on events published in the Okta System Log