Introducing the Okta Identity Engine: Customizable Building Blocks for Every Identity Experience
Passwordless authentication, progressive profiling, per-app branding and unlimited use cases now possible
Identity plays a significant role in nearly every digital trend, taking root in modern security approaches and digital transformation initiatives. Engineering, digital, IT and security teams have a wide array of different identity use cases across their customer and workforce experiences, and no identity product can be pre-defined to support exactly every use case required. Organizations instead require an easy, out-of-the-box way to tailor the basic building blocks of the identity experience, all while maintaining security.
“Every modern application relies on some form of identity and
authentication, but not every application will leverage identity in the
same way, or have the same requirements,” said
Identity Building Blocks Drive Unlimited Variety of User Experiences
The Okta Identity Engine enables organizations to use any number of
signals including application, device, network, and intent as context to
inform the identity journey of any user, adapting that identity
experience accordingly. For example, one identity journey of a new user
interacting with a low-risk application may minimize abandonment during
registration by asking for just a name and email address before
authorizing that user’s access. Another journey may require additional
identity verification steps and enroll a banking customer in
multi-factor authentication before authorizing access to a high security
app. It’s possible to create unlimited variations by applying different
context to policies within the Okta Identity Engine. Customization can
be done out-of-the-box via the
Possible use cases include:
- Passwordless Authentication: Rather than enrolling a password in an authentication sequence, organizations can use an email magic link to authenticate a user. Organizations can apply a passwordless flow to some applications, but for others, require a stronger factor, such as email, push or WebAuthn.
- Progressive Profiling: To prevent users from abandoning a site, enterprises can configure registration for less friction. Administrators can configure initial enrollment to limit additional attribute requirements for a user, while configuring another sequence to require that a user input a home address to access a certain resource. For example, an ecommerce site may want to ask for an email address when a user first engages, but then ask for a home address and phone number before making a purchase.
- Per-App Branding: Administrators can configure each sequence with different branding to provide a separate branded experience depending on how a user begins to use its services. For instance, a single hotel loyalty program serving multiple brands can implement per-app branding to customize the look and feel of logins depending on the customer’s hotel choice. This app-specific branding remains consistent through each unique sign-in, email, and push notification workflow.
“Albertsons interacts with over 34 million customers a week, providing
the products they want, at a fair price, with great customer service,”
said Ramiya Iyer, GVP, IT Digital, Data and Pharmacy,
Together, the Okta Identity Engine and the newly-announced
Availability
The Okta Identity Engine will be included in all existing
About
View source version on businesswire.com: https://www.businesswire.com/news/home/20190402005319/en/
Source:
Jenna Kozel King
press@okta.com