Finally, you can use
TypingDNA as 2FA in Okta

The actual TypingDNA experience is identical in both versions, however, the Standard integration is a standalone integration that does not need any IAM to work, while the OIDC integration can be used in Okta (and other IAM platforms in the future). Also the OIDC integration has no independent root of trust (RoT) and only comes with the Enterprise license. If you have any questions or doubts about the differences please contact us for more information.

Although we have solutions that work on mobile devices, particularly this OIDC integration is non-mobile only. The reason for that is that TypingDNA should be primarily used whenever a phone is not available, and as a better user experience since the user doesn’t have to switch devices to log in on a corporate computer. From an authentication flow perspective, users who log in from mobile devices are prompted with another available 2FA method suitable for the selected device. Note that in IAMs like Okta you can add very detailed rules and policies targeting not only mobile devices, but particularly different mobile operating systems.

Our solution still recognizes people even after some minor hand injuries, however, there are cases where you will not be recognized after such an event. In this case, a failed verification will occur and the user will be prompted to use another method available in the Authentication Policy.

SLA commitments are available for enterprise customers. Contact us to find more.

Unfortunately, the OIDC integration is not available as a live demo, please contact us to schedule a demo call.