Harrison 
Posted by: Gina Biernacki, Product Manager
Today, the Google Identity team announced a beta program for developers to test integration with the new FedCM (Federated Credential Management) API in the Chrome browser.
audience
This update is for all Google Identity Services (GIS) web developers who rely on the Chrome browser and use:
Why FedCM?
GIS now uses third-party cookies to make it easier for users to sign up and sign in to websites, and to make user sign-in more secure by reducing reliance on passwords. However, as part of the Privacy Sandbox initiative, Chrome will phase out support for third-party cookies in his 2024 to protect user privacy online.
The W3C FedID Community Group developed the FedCM API as a new privacy alternative to third-party cookies for federated identity providers. This new FedCM solution allows Google to continue providing a secure and streamlined experience for signing up and signing into his website via his GIS.
Benefits of FedCM include:
- Improved privacy. By design, FedCM prevents identity providers from viewing users’ activities on the web without their permission, keeping privacy at the center of user interactions.
- High quality user experience. FedCM allows GIS to rely on a new browser-native UI, resulting in a faster and more consistent sign-in experience for users across websites and identity providers. The new user experience provided by this browser takes inspiration from previous versions of her GIS library, making the transition easier for users and developers.
- Additional browser support. We expect other browsers to support FedCM, such as Firefox and other Chromium-based browsers such as Edge, Opera, and Samsung browsers. We’re excited to support a consistent and frictionless sign-in experience across the web.
What’s changing for GIS developers?
As a result of the Chrome browser’s plan to deprecate third-party cookies, developers using the One Tap and Auto Sign-In features in GIS are expected to migrate to FedCM within the next year. For most developers, this transition will be seamless through backward-compatible updates to the GIS JavaScript library. The GIS JavaScript library calls his FedCM API behind the scenes without requiring any developer changes. However, some websites may require minor changes, such as updating a custom layout or positioning the sign-in prompt. To see if your website requires changes, see our migration guide article. We also encourage you to participate in the FedCM Beta Program.
FedCM user experience details
With FedCM, your GIS continues to provide a seamless user experience even if third-party cookies are no longer available. The new FedCM API makes minimal changes to existing user flows and websites. The updated one-tap and automatic sign-in user prompts are shown below.
 |
| GIS One Tap User Experience with FedCM API |
 |
| Auto sign-in user experience using FedCM API |
Timeline
GIS will gradually migrate traffic to FedCM starting in November 2023, with minimal changes required for most developers. If your website uses GIS One Tap or Auto Sign-in, keep the following timeline in mind:
- August 2023: developers can participate in the GIS FedCM beta release. We also encourage all new apps to join her FedCM Beta from the beginning.
- Early 2024: To support Chrome Browser’s announced plans to block third-party cookies by default starting in late 2024, developer migration to FedCM will begin in stages, reaching 100% by mid-2024. Masu.
- Early 2024: Chrome plans to begin extensive testing of third-party cookie blocking ahead of the aforementioned plans.
If the Chrome browser blocks third-party cookies by default, GIS One Tap requires the use of FedCM to function.
Get ready by joining our beta program
We encourage all developers to test the FedCM API by participating in the currently available beta programs to prepare for upcoming changes. To get started with the program and learn more, visit the developer site and check the google-signin tag on Stack Overflow for technical support. developers, please send feedback about the FedCM beta program to gis-fedcm-feedback@google.com.
