The Duo Blog
Passwordless is a sea change in authentication. We’ve spent the last 60 years relying on shared secrets to access digital resources and moving away from that is no small task. However, the transition will be worth the effort. Passwordless authentication provides the rare opportunity to increase our access security drastically while simultaneously improving the user experience — a compelling prospect!
However, as someone researching this new technology, you might be overwhelmed with all of the buzz — asking questions like “How do I even get started?” or “Does everything have to change?!”
We’re excited to announce a public preview for Duo Passwordless using our Duo Single Sign-On solution — with a core focus on making this new technology as easy as possible to adopt in your organization.
See the video at the blog post.
We adhered to a few simple principles as we developed the product. It needed to:
- work for any user, on any device
- integrate with existing infrastructure
- and minimize setup time for both admins and end users.
Therefore, we’ve built out our feature set with each of these themes in mind.
To enable any user on any device, we’ve made sure that our passwordless solution supports platform biometrics on Mac, Windows, iOS, and Android. For users that don’t have access to a device with a built-in biometrics, we’ve added support for FIDO2 security keys that can verify users. Users can also enroll multiple passwordless authenticators. By offering several passwordless device options, we’re hoping to make it easy for users to get up and running with this new technology.
In order to flexibly fit into existing infrastructure, we’re offering several set-up options. We recommend using Duo SSO. It’s a cloud-delivered SSO solution that includes all of our deep security features. And for customers leveraging an existing SSO solution, we’ve built easy integrations so that you can use our passwordless functionality in those cases as well.
Finally, and this is key to our offering, we’ve made things easy to set up
[…]
Content was cut in order to protect the source.Please visit the source for the rest of the article.
Read the original article: