Adds support for the AuthenticatorSelectionCriteria.residentKey property to specify during Web Authentication API (WebAuthn) credential registration whether a client-side discoverable credential should be created. Also adds support for the WebAuthn "credProps" extension, which indicates to the Relying Party whether a created credential is client-side discoverable.
Support on Windows >= 1903 depends on Microsoft implementing it in Windows. Support on Android depends on Android's WebAuthn library supporting it. Android WebView does not support WebAuthn.
This feature will be supported by Chrome's Virtual Authenticator API implementation.
Support on Windows >= 1903 depends on Microsoft implementing it in Windows. Support on Android depends on Android's WebAuthn library supporting it. Android WebView does not support WebAuthn.
Contact emails
mart...@google.com, nsat...@chromium.org, a...@chromium.orgExplainer
https://github.com/w3c/webauthn/issues/991
Specification
https://w3c.github.io/webauthn/#dom-authenticatorselectioncriteria-residentkeyAPI spec
YesDesign docs
https://github.com/w3c/webauthn/pull/1191Summary
Adds support for the AuthenticatorSelectionCriteria.residentKey property to specify during Web Authentication API (WebAuthn) credential registration whether a client-side discoverable credential should be created. Also adds support for the WebAuthn "credProps" extension, which indicates to the Relying Party whether a created credential is client-side discoverable.
Blink component
Blink>WebAuthenticationTAG review
N/A (minor API change)
TAG review status
Not applicableRisks
Interoperability and Compatibility
Support on Windows >= 1903 depends on Microsoft implementing it in Windows. Support on Android depends on Android's WebAuthn library supporting it. Android WebView does not support WebAuthn.
Gecko: No signal
WebKit: No signal
Web developers: No signals
Debuggability
This feature will be supported by Chrome's Virtual Authenticator API implementation.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
NoSupport on Windows >= 1903 depends on Microsoft implementing it in Windows. Support on Android depends on Android's WebAuthn library supporting it. Android WebView does not support WebAuthn.
Is this feature fully tested by web-platform-tests?
Yes. (Pending CL:2508878)Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1117630Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5701094648840192Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/hHV_nrVc-To/m/fjcfKB7zBwAJThis intent message was generated by Chrome Platform Status.
--
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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAB%3DfcEa135x9a5h8oeNdqjD_%3D8uYC_EmL0Mnar4ncoUWO0pJKg%40mail.gmail.com.
--
On Fri, Nov 6, 2020 at 12:57 AM 'Martin Kreichgauer' via blink-dev <blin...@chromium.org> wrote:Contact emails
mart...@google.com, nsat...@chromium.org, a...@chromium.orgExplainer
https://github.com/w3c/webauthn/issues/991That's not an explainer. I'm sure I can get all that information from reading through the dozens of comments on the issue and the PR, but it'd be extremely helpful to me and other reviewers (as well as the general public) if you could sum up what this change is supposed to be doing, what are its implications on the API shape and how are developers supposed to be using it.If writing it up in an explainer is too much overhead for some reason and would be relatively short, an inline explanation would work as well.
Specification
https://w3c.github.io/webauthn/#dom-authenticatorselectioncriteria-residentkeyAPI spec
YesDesign docs
https://github.com/w3c/webauthn /pull/1191Summary
Adds support for the AuthenticatorSelectionCriteria.residentKey property to specify during Web Authentication API (WebAuthn) credential registration whether a client-side discoverable credential should be created. Also adds support for the WebAuthn "credProps" extension, which indicates to the Relying Party whether a created credential is client-side discoverable.
Blink component
Blink>WebAuthenticationTAG review
N/A (minor API change)That's not typically a valid reason to skip TAG review.Was the change reviewed by someone? (e.g. in a WG)
TAG review status
Not applicableRisks
Interoperability and Compatibility
Support on Windows >= 1903 depends on Microsoft implementing it in Windows. Support on Android depends on Android's WebAuthn library supporting it. Android WebView does not support WebAuthn.
Gecko: No signal
WebKit: No signalCould you ask for signals?
Web developers: No signalsDo we have reason to believe users of the API actually need this change and will use it once shipped?
LGTM1
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4a935331-8041-4389-a58c-a207ef15da87n%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fcc90e83-a54f-f758-8215-8b41c3d93abe%40gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3DdxA6Rt5ph1Ken%2B64vCUrjwFoXByaxEjDaWh3V41O%2BhcQ%40mail.gmail.com.
Alex's reasoning on TAG reviews seems to apply here as well. Could y'all ask for a TAG review?