You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the parsing of credential data is wrapped up within UmarshalJSON, which is inconvenient if one uses a binary encoding (I use gRPC/Protobuf) to communicate with the client. The Webauthn Browser API already exposes the values as ArrayBuffers, which can be directly encoded by Protobuf.
Something like this (adapted from the existing interface in UnmarshalJSON) could work:
typeRawAuthenticatorAttestationResponsestruct {
ClientDataJSON []byte// JSON-serialized client data passed to the authenticator by the client.AttestationObject []byte`json:"attestationObject"`// Attestation object, containing authenticator data and attestation statement.
}
typeRawPublicKeyCredentialstruct {
ID []byte// Credential IDResponseRawAuthenticatorAttestationResponse// Authenticator's response to client's request to create a public key credential.Typestring`json:"type"`// "public-key"
}
All []byte values would already be in binary.
The text was updated successfully, but these errors were encountered:
Currently the parsing of credential data is wrapped up within UmarshalJSON, which is inconvenient if one uses a binary encoding (I use gRPC/Protobuf) to communicate with the client. The Webauthn Browser API already exposes the values as ArrayBuffers, which can be directly encoded by Protobuf.
Something like this (adapted from the existing interface in UnmarshalJSON) could work:
All
[]byte
values would already be in binary.The text was updated successfully, but these errors were encountered: