[WebAuthn] Enable concurrent Authenticator requests where supported by the native API #6389
+351
−236
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
In certain situations it should be possible to make concurrent MakeCredential/GetAssertion calls. Therefore the authenticator being busy is no longer checked in the C# API. Instead, concurrent calls are unconditionally forwarded and it is now up to the native API whether it will honor the request or return an error.
Additionally, this pull request fixes an error in AuthenticatorAssertionResponse data marshalling.
API Changes