Wallix webauthn lib about simplewebauthn HOT 2 CLOSED

Hello @netmiller, this is a fun question for someone like me!

In absolute terms there shouldn't be anything about those existing credID's or publicKey (very specifically using wallix names here) that would prevent you from using them for WebAuthn response verification with other libraries like SimpleWebAuthn.

Talking specifically about SimpleWebAuthn, it looks like you're using base64 to store credential ID and public key bytes; so long as you convert them to Uint8Arrays when passing them into verifyAuthenticationResponse() as the value of options.authenticator.credentialID and options.authenticator.credentialPublicKey respectively then there shouldn't be a problem to use those existing credentials with SimpleWebAuthn.

FYI you can import isoBase64URL from @simplewebauthn/server/helpers and use its support for base64 if needed:

import { isoBase64URL } from '@simplewebauthn/server/helpers';

const verification = await verifyAuthenticationResponse({
  // ...
  authenticator: {
    credentialID: isoBase64URL.toBuffer(wallix.credID, 'base64'),
    credentialPublicKey: isoBase64URL.toBuffer(wallix.publicKey, 'base64'),
    counter: wallix.counter
  },
});

There's nothing isoBase64URL does that other base64 libraries don't already do. Put another way, use of isoBase64URL is not a requirement for working with SimpleWebAuthn, it's only offered as a resource for projects that might not already have pulled in such a base64url/base64 helper library.

from simplewebauthn.

I'm going to convert this into a discussion now as this isn't reporting an issue with SimpleWebAuthn.

from simplewebauthn.