*Contact emails* [email protected] *Explainer* https://github.com/w3c/webauthn/issues/2363
*Specification* https://github.com/w3c/webauthn/pull/2382 *Summary* The Web Authentication API specifies a series of webdriver commands to support testing. These commands set up "virtual authenticators" that behave as if they were connected to the user agent and can service WebAuthn operations. https://github.com/w3c/webauthn/pull/2382 introduced two changes related to signature counters: * The Add Credential command can now take a null `signCount` parameter. This specifies that the virtual authenticator will set the signature counter to zero on every subsequent get assertion operation, matching the behaviour of synced passkey providers. * A new `signCount` parameter to the Set Credential Properties command that lets callers override the signature counter on the authenticator to test simulated duplicated authenticators. We are requesting permission to ship these webdriver-only changes. Webdriver classic is a little special in that there doesn't seem to be a sane way to flag guard the changes (and developers can set whatever flags they want anyway!). Thus, in attempting to follow the exciting webdriver WP launch process, we are asking for permission *before *landing any code. *Blink component* Blink>WebAuthentication <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebAuthentication%22> *Web Feature ID* N/A *Motivation* Better support testing code that checks signature counters. *Initial public proposal* https://github.com/w3c/webauthn/issues/2363 *Search tags* webauthn <https://chromestatus.com/features#tags:webauthn>, webdriver <https://chromestatus.com/features#tags:webdriver>, signature counter <https://chromestatus.com/features#tags:signature%20counter> *TAG review* N/A This is a small webdriver feature. *TAG review status* Not applicable *Goals for experimentation* No experimentation. *Risks* *Interoperability and Compatibility* Safari and Firefox both support the automation API. Firefox isn't very active in the spec, but a webkit engineer has approved the spec change. *Gecko*: N/A Too small of a feature to wait for this. *WebKit*: N/A Too small of a feature to wait for this. *Web developers*: MasterKale@ (Duo / Cisco) authored the spec change. *Other signals*: *WebView application risks* Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? *No information provided* *Debuggability* This is a webdriver feature. *Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?* No On Chrome, the WebAuthn webdriver API is only supported on desktop. *Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* We'll land WPTs once the feature lands. I can't find any sane way to flag-guard a webdriver classic change of this nature. *Flag name on about://flags* None. *Finch feature name* None. *Non-finch justification* This is a webdriver feature. *Rollout plan* Will ship enabled for all users *Requires code in //chrome?* False *Tracking bug* https://crbug.com/533056772 *Estimated milestones* 153 *Anticipated spec changes* None. *Link to entry on the Chrome Platform Status* https://chromestatus.com/feature/4812056424480768?gate=6110516641660928 This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- Nina Satragno -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAB0jiomsDBgLmcFb-wKnMYiiD5YYGPKcecdAVS4ZnUOecX_9-g%40mail.gmail.com.
