@simplewebauthn/browser 7.0.0

v7.0.0 - The one that sets the library loose

on Node.js NPM

The highlight of this release is the rearchitecture of @simplewebauthn/server to start allowing it to be used in more environments than Node. This was accomplished by refactoring the library completely away from Node's Buffer type and crypto package, and instead leveraging Uint8Array and the WebCrypto Web API for all cryptographic operations. This means that, hypothetically, this library can now also work in any non-Node environment that provides access to the WebCrypto API on the global crypto object.

Existing Node support is still first-class! In fact because @simplewebauth/server still builds to CommonJS it will continue to be tricky to incorporate the library in non-Node, ESM-only environments that do not support CommonJS modules (whether natively, via a bundler, etc...) A future update will attempt to fix this to offer better support for use in ESM-only projects with support for WebCrypto (e.g. Deno).

Please read all of the changes below! There are significant breaking changes in this update and additional information has been included to help adapt existing projects to the newest version of these libraries.

Packages:

• @simplewebauthn/browser@7.0.0
• @simplewebauthn/server@7.0.0
• @simplewebauthn/typescript-types@7.0.0
• @simplewebauthn/iso-webcrypto@7.0.0

Changes:

• [server] A new "isomorphic" library architecture allows for use of this library in non-Node environments. In addition, the library now targets Node 16 and above (#299)
• [server] @simplewebauthn/server/helpers now includes several new helpers for working with WebAuthn-related data types that should work in all run times:
  • isoCBOR for working with CBOR-encoded values
  • isoCrypto for leveraging the WebCrypto API when working with various WebAuthn/FIDO2 data structures
  • isoBase64URL for encoding and decoding values into base64url (with optional base64 support)
  • isoUint8Array for working with Uint8Arrays
  • cose for working with COSE-related methods and types
• [server] Certificate chains using self-signed X.509 root certificates now validate more reliably (#310)
• [server] Code execution times for some common use cases are approximately 60-90% faster (#311, #315)
• [iso-webcrypto] This new library helps @simplewebauthn/server reference the WebCrypto API in more environments than Node. This package is available on NPM, but it is not officially supported for use outside of @simplewebauthn/server!

Breaking Changes

• [server] The following values returned from verifyRegistrationResponse() are now a Uint8Array instead of a Buffer. They will need to be passed into Buffer.from(...) to convert them to Buffer if needed:
  • aaguid
  • authData
  • clientDataHash
  • credentialID
  • credentialPublicKey
  • rpIdHash
• [server] The following values returned from verifyAuthenticationResponse() are now a Uint8Array instead of a Buffer. They will need to be passed into Buffer.from(...) to convert them to Buffer if needed:
  • credentialID
• [server] The isBase64URLString() helper is now isoBase64URL.isBase64url()
• [server] The decodeCborFirst() helper is now isoCBOR.decodeFirst()
• [server] The convertPublicKeyToPEM() helper has been removed
• [typescript-types] [server] [browser] New JSON-serialization-friendly data structures added to the WebAuthn L3 spec have been preemptively mapped into this project. Some types, values, and methods have been refactored or replaced accordingly (#320):
  • The RegistrationCredentialJSON type has been replaced by the RegistrationResponseJSON type
  • The AuthenticationCredentialJSON type has been replaced by the AuthenticationResponseJSON type
  • RegistrationCredentialJSON.transports has been relocated into RegistrationResponseJSON.response.transports to mirror response structure in the WebAuthn spec
  • The verifyRegistrationResponse() method has had its credential argument renamed to response
  • The verifyAuthenticationResponse() method has had its credential argument renamed to response
• [server] generateRegistrationOptions() now marks user verification as "preferred" during registration and authentication (to reduce some user friction at the browser+authenticator level), and requires user verification during response verification. See below for refactor tips (#307)

const verification = await verifyRegistrationResponse({
  credential: attestationFIDOU2F,
  // ...
});

const verification = await verifyRegistrationResponse({
  credential: attestationFIDOU2F,
  // ...
  requireUserVerification: false,
});

const verification = await verifyAuthenticationResponse({
  credential: assertionResponse,
  // ...
});

const verification = await verifyAuthenticationResponse({
  credential: assertionResponse,
  // ...
  requireUserVerification: false,
});

• [server] generateRegistrationOptions() now defaults to preferring the creation of discoverable credentials. See below for refactor tips (#324)

const options = generateRegistrationOptions({
  rpName: 'SimpleWebAuthn',
  rpID: 'simplewebauthn.dev',
  userID: '1234',
  userName: 'usernameHere',
});

const options = generateRegistrationOptions({
  rpName: 'SimpleWebAuthn',
  rpID: 'simplewebauthn.dev',
  userID: '1234',
  userName: 'usernameHere',
  authenticatorSelection: {
    // See https://www.w3.org/TR/webauthn-2/#enumdef-residentkeyrequirement
    residentKey: 'discouraged',
  },
});