Google is working to banish more passwords. Chrome 67 is released for the desktop to bring the Web Authentication standard. Firefox allows password-free sign-ins (such as USB keys) via virtually any website without having access to specific services. Now the best browser (probably the best based on user review) also support hassle-free logins. Chrome password now supports the features.
The Generic Sensor API lets web apps talk to sensors in devices like VR headsets and fitness trackers. A 3D world is possible to enjoy by just moving your head or wrist.
How Chrome password supports “password-free” logins?! Chrome password now supports more password-free sign-ins in google chrome
Google’s Chrome browser enabled the FIDO (Fast IDentity Online) U2F standard in Chrome 67, which includes support for the new WebAuthn standard. If you previously used physical security keys to log into Facebook and Google, they won’t need a replacement, given WebAuthn is backward compatible.
The FIDO Alliance working together to free passwords since 2014. Cryptographic keys relies for login credentials which never stored on your device. FIDO U2F and FIDO2 standards rely on secondary devices, like Yubico’s Security Key and YubiKey NEO USB-based devices, to create these cryptographic keys.
The idea behind WebAuthn is to bring the cryptographic key creation and exchange directly to the browser. Prior to WebAuthn support, logins rely on passwords even though you don’t need to enter credentials each time you log onto a service: Physical security keys and biometric devices merely “authenticate” those credentials. But with WebAuthn support in place, you sign into an account only with a username: No password is required.
The Web Authentication API is an extension of the Credential Management API that enables strong authentication with public key cryptography, enabling password-less authentication and/or secure second-factor authentication without SMS texts.
Many websites already have pages that allow users to register new accounts or sign in to an existing account, and WebAuthn acts as a replacement or supplement to those on those existing web pages. Similar to the other forms of the Credential Management API, the Web Authentication API has two basic methods that correspond to register and login:
navigator.credentials.create() – when used with the public key option, creates new credentials, either for registering a new account or for associating a new asymmetric key pair credential with an existing account.
navigator.credentials.get() – when used with the public key option, uses an existing set of credentials to authenticate to a service, either logging a user in or as a form of second-factor authentication.
Note: both create() and get() require a Secure Context (e.g. – the server is connected by https or is the localhost), and will not be available for use if the browser is not operating in a secure context.
How Chrome password supports “password-free” logins and Firefox Password Free Login works out, is described https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API. If you’re interested enough to read elaborately then go through.