Authentication API is a flexible interface that allows clients to verify user
identity by their typing
through requests to a RESTful API. While 2FA is a common use-case for the Authentication
API, it isn’t a
constraint, and the product can be leveraged within an application flow wherever a
user’s typing behavior
requires confirmation. The Authentication API is limited to enrolling and verifying
typing patterns, and does
not include managed OTP features (One Time Passwords/also known as 2FA codes) among
other things.
Verify 2FA is a product that uses the Authentication API as a core technology but has
multiple other features and
limitations. There is a standard/stand alone version and an OIDC version (for IAM
platforms such as Okta, Ping,
etc). The standard Verify 2FA solution is a managed OTP replacement product for
companies that don’t use an
external IAM platform but want to add a robust 2FA to their login systems. Designed with
frictionless,
cost-effective authentication in mind, Verify 2FA combines typing behavior verification
with intelligent OTP
features in one solution. In Verify 2FA, users authenticate with their typing behavior
(by typing 4 words). OTP
codes for identity verification are only leveraged in necessary scenarios, such as a
typing failure, suspected
fraud or initial enrollment. By deferring to OTP codes as a secondary factor, Verify 2FA
improves UX while
drastically reducing the number of SMS or Email OTP codes required to be sent.
The Verify 2FA OIDC integration is a particular case of Verify 2FA that does not use
OTPs as Root of Trust, but
integrates with other platforms (such as Okta or Ping Identity) and allows the user to
enroll and login from the
integrated platform. In this case Verify 2FA is a 2FA/MFA method that can be used as an
authenticator.