Fwd: Intent to Implement: Web Authentication API for Chrome

FYI.

On Friday, November 11, 2016 at 1:18:17 PM UTC-8, Kim wrote:
>
> Contact emails
>
> kpaulhamus@chromium.org <javascript:>, aczeskis@chromium.org, 
> <javascript:> juanlang@chromium.org <javascript:>, piperc@chromium.org 
> <javascript:>
>
> Spec
>
> Editor's draft <https://w3c.github.io/webauthn/>
>
> Summary
>
> An API to allow the creation and use of strong, attested, cryptographic scoped 
> credentials <https://w3c.github.io/webauthn/#scoped-credential> by web 
> applications, for the purpose of strongly authenticating users. 
>
> Motivation
>
> The Web Authentication API is a new web standard that subsumes FIDO U2F 
> and provides additional non-phishable authentication capabilities. The 
> initial implementation of the spec will allow migration of current U2F API 
> callers from the existing Chrome component extension -- allowing Chrome to 
> eventually deprecate the extension. This implementation would also serve as 
> one of the 2 implementations needed for standards viability.
>
> Some platforms may provide partial implementations of the Web 
> Authentication specification (e.g., for communicating with Authenticators) 
> -- in such cases Chrome will try to use these APIs.
>
> Interoperability and Compatibility Risk
>
> Firefox: In development
>
> Edge: In development
>
> Safari: No public signals
>
> Web developers: No public signals
>
> Low. We don’t intend to ship until we demonstrate interoperability with 
> Firefox for a standardized version of the spec.
>
> Ongoing technical constraints
>
> None.
>
> Will this feature be supported on all six Blink platforms (Windows, Mac, 
> Linux, Chrome OS, Android, and Android WebView)?
>
> This feature will be supported on all platforms except for Android WebView.
>
> OWP launch tracking bug
> https://crbug.com/664630
>
> Link to entry on the feature dashboard <https://www.chromestatus.com/>
> https://www.chromestatus.com/feature/5669923372138496
>
> Requesting approval to ship?
>
> No.
>
>