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
So AuthenticatorAttestationResponse struct contains only minimal fields which might be sent in JSON, but it looks the spec allows additional fields (which are just extracted from attestationOjbect):
The issue I have is that I send AuthenticatorAttestationResponse over the wire in JSON from the client. And client adds those fields. But on the server I want to use JSON unmarshal with DisallowUnknownFields set (primarily to detect changes in API I should check and possibly adapt to). And this is then currently not possible.
So I wonder if struct should define those additional optional fields, but not use them/ignore them?
Use Case
No response
Documentation
No response
The text was updated successfully, but these errors were encountered:
We will add the specific fields mentioned, but will purposefully decline to officially support DisallowUnknownFields due to the extensible and evolving nature of the specification itself.
Description
So
AuthenticatorAttestationResponse
struct contains only minimal fields which might be sent in JSON, but it looks the spec allows additional fields (which are just extracted fromattestationOjbect
):The issue I have is that I send
AuthenticatorAttestationResponse
over the wire in JSON from the client. And client adds those fields. But on the server I want to use JSON unmarshal withDisallowUnknownFields
set (primarily to detect changes in API I should check and possibly adapt to). And this is then currently not possible.So I wonder if struct should define those additional optional fields, but not use them/ignore them?
Use Case
No response
Documentation
No response
The text was updated successfully, but these errors were encountered: