Federated Credential Management (FedCM), will enable sign-in for the Google Identity Services (GIS) library after the phase out of third-party cookies.
Overview
The article discusses the migration to Federated Credential Management (FedCM) for Google Identity Services (GIS), emphasizing the importance of this transition as third-party cookies are phased out. It outlines the migration timeline, the impact on developers, and encourages experimentation with the new FedCM API.
What You'll Learn
1
How to prepare your website for the FedCM migration
2
Why the FedCM API is essential for future sign-in experiences
3
When to expect automatic migration to FedCM for your GIS features
Key Questions Answered
What is the timeline for migrating to FedCM?
The migration to FedCM will begin in April 2024 for websites without cross-origin iframe and Content Security Policy issues, with subsequent phases in July and October 2024 for those with issues. This timeline is crucial for developers to prepare their websites for the transition.
How does the FedCM API improve user experience?
The FedCM API allows for a privacy-preserving alternative to third-party cookies, enabling secure and streamlined sign-in experiences for users. It enhances user privacy while maintaining the ease of signing up and signing in to websites.
What changes might developers need to make during the migration?
Developers with custom integrations may need to update their sign-in prompts or layouts, especially if they use embedded iframes or have non-compliant Content Security Policies. It's recommended to review the migration guide for specific requirements.
Technologies & Tools
API
Federated Credential Management
Used as a privacy-preserving alternative to third-party cookies for federated identity providers.
API
Google Identity Services
Provides One Tap and Automatic Sign-In features that will migrate to FedCM.
Key Actionable Insights
1Developers should start testing the FedCM API as soon as possible to ensure their sign-in flows remain uninterrupted during the migration.By experimenting with the FedCM API now, developers can identify potential issues and make necessary adjustments before the automatic migration occurs in April 2024.
2It's crucial to stay informed about the migration timeline and be proactive in making any required changes to your website.Understanding the timeline helps developers plan their updates effectively, ensuring compliance with the new FedCM requirements and avoiding disruptions.
3Consider temporarily exempting your traffic from using FedCM if you need more time for verification and adjustments.This exemption is available until February 2025, allowing developers to ensure their systems are fully compatible with the new API before it becomes mandatory.
Common Pitfalls
1
Failing to review and update custom integrations may lead to broken sign-in flows after migration.
Websites that rely on specific layouts or embedded iframes need to ensure compatibility with FedCM. Developers should proactively check their implementations against the migration guide.