Known issue - Fix delivered - Notifications not received on Authenticator Desktop

What is the issue?

The registration for receiving notifications does not work correctly for new installations of Authenticator for Windows, Linux, and macOS since approximately August 8th.

Root cause

The root cause analysis is completed. The issue was found to be related to the deprecation of Google's Firebase FCM Legacy APIs (for notification sending), replaced by the FCM API V1. TrustBuilder implemented changes in June in order to support the FCM API V1 with no impact on Authenticator. Analysis confirmed that one Legacy API was still being used in Authenticator code base and that the process of decommissioning this API by Google had started in August and is ongoing.

Who is/is not impacted?

Impacted: The new installations of Authenticator for Windows, Authenticator for macOS and Authenticator for Linux. Both the latest version and previous versions of Authenticator.

Not impacted:

• The existing installations of Authenticator for Windows, macOS and Linux continue to receive notifications

• Authenticator for Android and for iOS continue to receive notifications, including new installations

Current workaround

The issue is only about notifications. The authentication session is valid and the users can authenticate using the Authorize a connection button located in the home of the Authenticator app.

Recommendations

• Upgrade your users to 6.38.0

• For the users that cannot upgrade, or did not upgrade yet, make sure to provide the above information about “Authorize a connection” so they are able to authenticate