9/12/2023 0 Comments Fido u2f security key googleThe U2F API depreciation means that services will need to migrate to the WebAuthn API to continue supporting phishing-resistant, multi-factor authentication (MFA) with the YubiKey on their services. The WebAuthn spec was designed with backward compatibility in mind so that U2F will work with WebAuthn. These two protocols might not look related, but U2F is the precursor to WebAuthn. Since that time, the WebAuthn protocol has been adopted. The original way of implementing U2F with Chrome was through the U2F API. The forthcoming update means only the U2F API is being deprecated and that authentication with the U2F protocol will continue to be supported with the WebAuthn API. The important aspect to note is that U2F means two things in Chrome: it is an authentication protocol as well as an API. What does this mean, and how will it affect my users? Additionally, please register for our February 22nd webinar where we will dive deep into this topic in an interactive WebAuthn session. If you’re impacted by this change, and want to learn more, read below for details on how to mitigate this issue. If your organization is currently utilizing U2F in your product or web-based service, with some planning and simple code updates, you’ll continue to be able to provide user continuity and get your services switched to the WebAuthn API in Chrome, all while maintaining compatibility with existing YubiKeys. With Yubico’s commitment to keeping our customers updated on the latest in changes to security protocols, we wanted to be sure you are aware that Chrome has deprecated the Universal 2nd Factor (U2F) API, and will be removing it entirely with the Chrome v. Some changes are exciting, like providing new features and broader support, while other changes can be a minimal bump in the road or, in extreme cases, cause adverse effects on end users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |