Okta Hooks
Every person, every technology, every identity journey is different and requirements are constantly changing. Organisations need to create deep integrations across their technology ecosystem, driven by identity.
There are two types of Hooks:
Event Hooks
Send Okta events to your systems as they occur
Inline Hooks
Modify inflight Okta processes with custom logic
Event Hooks
Event Hooks send Okta events of interest to your systems via HTTP POST as they occur, just like a webhook. A developer can write additional logic to notify or kick off workflows within downstream services.
Potential customisations using Event Hooks include:
- Push newly registered user to the rest of your marketing technology stack, including email marketing systems, analytics, CRM, data warehouse, etc
- After a user registers in Okta, complete the account creation process across backend systems
- Sync user profile updates into downstream data stores Upon user deletion in Okta, begin the process of deleting user data in other related systems
- Notify an IT Slack channel of suspicious activity
- Push Okta events to SIEMs Notify an Admin when group membership or app assignment changes
In the future, the recently-announced Azuqua acquisition will provide a no-code capability so that non-developers can build Hooks integrations as well.
Inline Hooks
Inline Hooks allow developers to modify inflight Okta processes with custom logic and data from a non-Okta source. Currently, the following Okta workflows can be modified:
Registration Inline Hook
Extend Self-Service Registration with external custom logic or 3rd party services to modify and validate profiles before completing registration.
Potential customisations using the Registration Inline Hook include:
- Validate user against existing database
- Enrich profile with information from a CRM or other directory
- Identity proofing with Experian
- Generate unique Customer ID
Import Inline Hook
Easily migrate customer and employee profile data from existing user stores with customisable data clean up and profile enrichment. Combine data from multiple sources into Okta’s centralised Universal Directory.
Potential customisations using the Import Inline Hook include:
- Enrich profile with information from a CRM, HR system or AD/LDAP
- Override Okta's default matching logic
- Identify username conflicts and create a unique one
Token and SAML Inline Hooks
Retrieve and use information housed in external systems in authorisation decisions.
Potential customisations using Token and SAML Inline Hooks include:
- Add sensitive customer data to tokens and assertions
- Retrieve dynamic customer data
- Integrate with external entitlement engines
Okta has long been a partner to ThoughtWorks for delivering innovative features to help us securely manage our enterprise identities. The introduction of Okta Hooks has enabled us to seamlessly incorporate identity events triggered by Okta into our existing event-driven architecture. We are excited for all the possibilities this opens up for tackling more complex workflows and elaborate integration scenarios.
Phil Ibarrola
TechOps Head of Technology
