It allows servers to integrate with the strong authenticators now built into devices, like Windows Hello or Apple’s Touch ID. Instead of a password, a private-public keypair (known as a credential) is created for a website. The private key is stored securely on the user’s device; a public key and randomly generated credential ID is sent to the server for storage. The server can then use that public key to prove the user’s identity.
Click here for additional information - Duo's guide to passkeys/Webauth
It allows servers to integrate with the strong authenticators now built into devices, like Windows Hello or Apple’s Touch ID. Instead of a password, a private-public keypair (known as a credential) is created for a website. The private key is stored securely on the user’s device; a public key and randomly generated credential ID is sent to the server for storage. The server can then use that public key to prove the user’s identity.
The downside of webauth or passkeys is that the site can only be accessed and approved by the device you set up the webauth or passkey.
UHV IT strongly recommends using the Duo Mobile app or getting a Duo hardware token. If you need a hardware token, please visit the UHV Connect Store. If you are in need of financial assistance, please fill out the Duo Hardware Token Financial Assistance Request form.
Click here for additional information - Duo's guide to passkeys/Webauth
It allows servers to integrate with the strong authenticators now built into devices, like Windows Hello or Apple’s Touch ID. Instead of a password, a private-public keypair (known as a credential) is created for a website. The private key is stored securely on the user’s device; a public key and randomly generated credential ID is sent to the server for storage. The server can then use that public key to prove the user’s identity.
Click here for additional information - Duo's guide to passkeys/Webau