Change description:
Implement the web authentication API for Chrome.
Changes to API surface:
Introduction of authentication.makeCredential and authentication.getAssertion interfaces.
Links:https://w3c.github.io/webauthn/Support in other browsers:Internet Explorer: In development
Firefox: In development
If there is a PM helping out with this I'd recommend you chat to them about setting up a type=launch issue for this.
type=launch issues are needed for any changes with security/privacy/ui/legal/etc changes and are separate to the launch-owp issues (type=launch are Google-private and for approvals, type=launch-owp are public and for community and cross-browser tracking of standards and implementation aspects)
If there isn't, feel free to reach out to the closest PM to you and cc me over email and we can work out what to do.
Once a type=launch issue is created please link to it from here and mark it as blocking this issue so we ensure it gets finished before this launches.
Also for more context on type=launch vs type=launch-owp issues you can see this doc: https://drive.google.com/open?id=1Z9x-PBYgDaR99tsNLvhibZLeAwDR757Gor--I60ygeE
I had pre-empted https://github.com/w3c/webauthn/pull/344 to rename Account. We actually ended up with RelyingPartyUserInfo, which I'll update in the implementation.
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.
We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.
For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit
For any questions, please contact owencm, sshruthi, larforge
The WebAuthn spec is still being iterated upon. During a recent WebAuthn interop, the 3 participating browsers had a similar level of implementation.
I do not believe the statement "Edge has had it implemented for a while." is correct.
To answer your original question: yes, progress is being made.
Comment 1 by owe...@chromium.org
, Nov 17 2016