Chrome FIDO U2F API Deprecation for RapidIdentity
FIDO AUTHENTICATION METHODS UPDATE
Google Chrome version 98 will disable the legacy U2F API by default, and these are used to interact with security keys that are used by RapidIdentity for FIDO authentication.
RapidIdentity Cloud and RapidIdentity LTS are being updated to utilize the Web Authentication API as recommended by Google, and will be available prior to the stable version of Google Chrome 98 that is expected in early February 2022. However, until the updates are released, there are several workarounds that can be utilized as well, including:
- Using an alternative authentication method in RapidIdentity (e.g., PingMe, OTP, QR Code, etc.)
- Using an alternate browser such as Mozilla Firefox or Apple Safari
- Enrolling your RapidIdentity Portal in the Google Chrome Origin Trial will allow sites to use U2F API, and will suppress deprecation prompts on the enrolled pages. The Origin Trial will extend the U2F API until July 26, 2022, shortly before the release of Chrome 104.
- Using the Google Chrome U2fSecurityKeyApiEnabled enterprise policy to suppress the depreciation prompts and keep the U2F API enabled on all devices within your organization.
Please remember to monitor the RapidIdentity Cloud and RapidIdentity LTS product release notes for more information.
For more information on Google’s announcement please click here.