of Okta – For Recipient’s Internal Use Only. @oktaDev | @deepu105 | deepu.tech WebAuthn == W3C specification WebAuthn is the specification that allows for passkeys implementation
of Okta – For Recipient’s Internal Use Only. @oktaDev | @deepu105 | deepu.tech Passkeys == Passwordless FIDO credential with WebAuthn. It uses asymmetric public key cryptography
of Okta – For Recipient’s Internal Use Only. @oktaDev | @deepu105 | deepu.tech Passkeys Synced Hardware bound • Private key synced between devices in same ecosystem and backed up to cloud • Better usability • One time enrollment • Can be restored on device loss or on new device • Less secure than hardware bound passkeys • Private key stored only on the device • Not as convenient as synced passkeys • Each device needs enrollment • No recovery or backups • Most secure option
with: • Credential Management Level 1 • FIDO 2.0 Client to Authenticator Protocol 2 Illustration based on https://webauthn.me/introduction User interaction
Remote attack resistant • Breach resistant • Not reusable • Not shareable* • Superior to password + traditional MFA • Require biometric or physical keys
and FIDO2 • Can be synced or hardware-bound • Discoverable by browsers • Can be used for account registration as first factor • Enrollment required only once for synced passkeys FIDO MFA • Implemented using WebAuthn and FIDO2 • Only hardware bound • Not discoverable • Can only be second factor after account registration with password • Enrollment required on each device Passkeys vs FIDO MFA
validation Supports all attestation formats Suitable for relying party server implementation Supports passkeys Used by Keycloak and Spring Security Kotlin friendly Java WebAuthn libraries java-webauthn-server Not 100% FIDO2 conformant Supports attestation validation All attestation formats not supported Suitable for relying party server implementation Supports passkeys From Yubico