Investigate if it is possible for JSON to avoid base64 in js/json about webauthn-rs HOT 3 CLOSED

For conformance particularly, assume everyone wants base64url encoding without padding.

from webauthn-rs.

The spec was unclear (or I missed it?) about the base64 as url-safe or not. At the moment I attempt both url and standard, and fail only if both fail. I've opened a seperate issue to handle this issue.

This issue is more about the fact that there are a number of ArrayBuffer types that I just can't seem to handle nicely with Serde, so as a result my client js and server are base64'ing data that perhaps should not be. For example, the rawId in authenticate I am base64 encoding, making it equivalent to Id field.

So to be properly compliant with "any javascript client" parts, I should not require base64 on these arrayBuffer types incorrectly. :)

from webauthn-rs.

Closing because it's not possible to create json types that can become a Uint8Array on a browser. You must base64 these datafields. It surprises me that the webauthn standard does not just say "base64 these" and then leave it to the navigator.credentials api to handle it, but alas, instead all javascript implementations now have the extreme joy of working out how to get from base64 to a uint8Array and tampering with the internals of any server issued request.

from webauthn-rs.