Re: [webauthn] `CredentialRequestOptions` make otherwise valid values invalid in an undesirable way

In discussion on webauthn call, it seems that we ought to add to the beginning of #createCredential and #getAssertion algs a step that checks for "required" options dictionary memebers' presence and bail out if any are not present.  Also need to make determination whehter we wish to convert present "required" dict members to having defalt NULL values, or no default values (but with comments indicating "requiredness").

GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 3 October 2018 17:35:46 UTC