Google starts rolling out Passkey scan login support for Android and Chrome

Apple, Google, Microsoft, and others in the industry want to replace website/app passwords with “Passkeys” that simply require you to unlock your device.

Starting today, Android and Google Chrome will support logging in with this password. Google equates the experience of using Passports to existing password managers, where you just need to confirm your personal device password/fingerprint and the system will automatically enter the saved credentials to the mechanism that requires you to log in.

Google starts rolling: Likewise, Passkey can be securely backed up and synced to the cloud to “prevent locking in case of device loss”.

The two features announced today are for early adopters who have joined the Google Play Services beta and are using Chrome Canary, with a stable release coming “later this year.”

Users can create and use Passkeys on Android devices, and developers can build Passkey support on Android and other platforms with the Chrome browser through the WebAuthn API.

To create a Passkey on a compatible service, first confirm Passkey account information, then unlock your personal device with your fingerprint, face, or password.

Again, the login process only requires selecting the correct account and corresponding unlocked phone .

Log in to your desktop/laptop with the pass on your phone, a process that involves scanning a QR code.

Google starts rolling out Passkey scan login support for Android and Chrome

Google starts rolling out Passkey scan login support for Android and ChromeGoogle starts rolling out Passkey scan login support for Android and ChromeGoogle starts rolling out Passkey scan login support for Android and Chrome

For example, Android users can now log into a Passkey-enabled website using the Safari browser on a Mac. Likewise, Chrome users on Windows can do the same with Passkeys stored on their iOS devices.

In addition to the stable channel release of these features, Google will also release an API for native Android apps this year so that mobile apps can take advantage of network passwords.

Passwords created through the web API will work seamlessly with applications affiliated with the same domain name and vice versa.

The native API will provide a uniform way for applications to let users choose a password (if they have one) or a saved password.

This shared experience for both types of users facilitates the transition to Passport.

Going forward, on the Android side, third-party credential managers will be able to support Passports for their users “next year”.




DISCLAIMER OF COSFONE.COM