Google Identity services to transition to privacy-focused Sign-in with FedCM
Facing the phase-out of third-party cookies in Chrome due to privacy concerns, Google Identity Services (GIS) will transition to a new sign-in method called Federated Credential Management (FedCM).
![Google Identity services to transition to privacy-focused Sign-in with FedCM](/content/images/size/w1200/2024/02/Google-Sign-In.webp)
Facing the phase-out of third-party cookies in Chrome due to privacy concerns, Google Identity Services (GIS) will transition to a new sign-in method called Federated Credential Management (FedCM).
The update aims to offer a secure and private experience for users while maintaining seamless functionality for developers.
Starting April 2024, most GIS developers utilizing features like "One Tap" and "Automatic Sign-In" will automatically migrate to FedCM through backward-compatible updates to the GIS library. No developer changes are required for most cases.
While the transition will be smooth for most, websites with custom integrations may require minor adjustments, such as updating sign-in layouts or addressing Content Security Policy issues. Google encourages all developers to test FedCM functionality using the beta program to ensure compatibility and avoid potential disruptions.
Developers can opt-in to the FedCM beta program to verify their website's functionality and make any necessary adjustments before the automatic migration in April. Additionally, a temporary opt-out option allows developers needing more time to adapt before browser enforcement of third-party cookie restrictions.
Key Dates and Resources:
- January 2024: Chrome began limited testing of third-party cookie restrictions.
- April 2024: GIS begins migrating websites to FedCM on Chrome.
- Q3 2024: Chrome gradually restricts third-party cookies, reaching full enforcement by Q4.
- FedCM Mandatory: Once Chrome fully restricts third-party cookies, FedCM becomes mandatory for websites using "One Tap" and "Automatic Sign-In" features.
For detailed information and support, developers can visit the Google Developer Site, utilize the "google-signin" tag on Stack Overflow, or provide feedback via email.
This transition to FedCM signifies Google's commitment to offering a secure and privacy-focused sign-in experience for users while supporting developers in adapting to evolving web technologies.