Google Identity Services 即将迁移到 FedCM API。请按照
迁移指南查看可能发生的更改,并避免对网站的登录产生负面影响。
“使用 Google 帐号登录”版本说明
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
本页列出了 Google Identity Services JavaScript 库的新功能和重大变更。
2025-03-17
2024-12-01
2023-12-21
适用于 Google Identity 服务的 Federated Credential Management (FedCM) Beta 版已于 2023 年 8 月发布。许多开发者都测试了该 API,并提供了宝贵的反馈。
Google 从开发者那里收到的回复之一与 FedCM 自动登录流程用户手势要求有关。为了更好地保护隐私,Chrome 要求用户在每次使用 Chrome 实例时重新确认是否要使用 Google 账号登录网站,即使用户在 FedCM 发布之前已批准该网站也是如此。用户只需点击一次“一键式登录”提示,即可完成这项一次性重新确认,以表明其有意登录。这项变更可能会导致部分网站的自动登录转化率在最初出现中断。
近期,Chrome 在 M121 中对 FedCM 自动登录流程用户体验进行了更改。只有在第三方 Cookie 受到限制时,才需要重新确认。这意味着:
在第三方 Cookie 限制全面实施之前(如需了解最新时间表,请参阅“隐私沙盒”动态和更新页面),对于回访用户,FedCM 自动登录无需重新确认。如果用户通过 FedCM 界面重新确认,此重新确认将计入用户手势要求。
当用户手动限制第三方 Cookie 时(目前),或在未来的 Chrome 中默认限制第三方 Cookie 时,FedCM 自动登录功能会检查确认状态。
鉴于此项变更,我们建议所有自动登录开发者尽快迁移到 FedCM,以减少对自动登录转化率的影响。
对于自动登录流程,GIS JavaScript 不会在较低版本的 Chrome(M121 之前)上触发 FedCM,即使您的网站选择启用 FedCM 也是如此。
2023-08-15
2022-04-12
2021-4-13
2021-03-17
2020-3-24
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-03-17。
[null,null,["最后更新时间 (UTC):2025-03-17。"],[[["\u003cp\u003eGoogle Identity Services JavaScript library now supports Federated Credential Management (FedCM) to improve automatic sign-in flows, though reconfirmation may be required initially for enhanced privacy.\u003c/p\u003e\n"],["\u003cp\u003e"Sign in with Google" button now supports Family Link and adheres to Google Workspace policies.\u003c/p\u003e\n"],["\u003cp\u003eAMP support has been removed when FedCM is enabled.\u003c/p\u003e\n"],["\u003cp\u003eChrome users may need to reconfirm sign-in with Google Account in each instance for privacy reasons, with exceptions based on third-party cookie settings.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers are encouraged to migrate to FedCM to minimize potential disruptions to automatic sign-in conversion rates.\u003c/p\u003e\n"]]],[],null,["# Sign In With Google Release Notes\n\nThis page contains a list of the new features and significant changes to the\nGoogle Identity Services JavaScript library.\n\n2025-03-17\n----------\n\n- [Sign in with Google button](/identity/gsi/web/guides/personalized-button) supports [Federated Credential Management (FedCM)](https://developers.google.com/privacy-sandbox/cookies/fedcm) and adhere to [Google Workspace](https://workspace.google.com/) policies set by the organization's administrator.\n\n2024-12-01\n----------\n\n- [Sign in with Google button](/identity/gsi/web/guides/personalized-button) supports [Family Link](https://families.google/familylink/) and adhere to [Google Workspace](https://workspace.google.com/) policies set by the organization's administrator.\n\n2023-12-21\n----------\n\n- [Federated Credential Management (FedCM) Beta](https://developers.googleblog.com/2023/08/announcing-federated-credential-management-beta-for-gis.html) for Google Identity\n Services was launched in August 2023. Many developers tested the API and have\n provided valuable feedback.\n\n One response Google heard from developers is about the FedCM automatic sign-in\n flow user gesture requirement. For improved privacy, Chrome requires users to\n reconfirm that they want to sign in to the website with Google Account in each\n Chrome instance even if the user approved the website prior to the FedCM\n rollout. This one-time reconfirmation is achieved through a single click of\n the One Tap prompt to demonstrate user intent to sign-in. This change may\n cause an initial disruption in automatic sign-in conversion rates for some\n websites.\n\n Recently in M121, Chrome made a [change](https://developers.google.com/privacy-sandbox/3pcd/fedcm-updates#chrome_121_december_2023) to the FedCM automatic sign-in\n flow UX. The reconfirmation is only required when third-party cookies are\n restricted. This means:\n 1. Before third-party cookie restrictions are ramped up to 100% (see Privacy\n Sandbox [News and Update](https://privacysandbox.com/news/) page for latest timeline),\n FedCM automatic sign-in does not require reconfirmation for returning users.\n If users reconfirm with FedCM UI, this reconfirmation will count toward the\n user gesture requirement.\n\n 2. FedCM automatic sign-in will check the confirmation status when the\n third-party cookies are manually restricted by users today, or by default in\n future Chrome.\n\n With this change, we recommend all automatic sign-in developers migrate to\n FedCM as soon as possible, to reduce disruption to automatic sign-in\n conversion rates.\n\n For the automatic sign-in flow, GIS JavaScript won't trigger FedCM on an older\n Chrome (before M121), even if your website chooses to opt-in to FedCM.\n\n2023-08-15\n----------\n\n- Added [support](/identity/gsi/web/guides/supported-browsers#third-party_cookies) for the Federated Credential Management API (FedCM).\n- [Accelerated Mobile Pages](/identity/gsi/web/amp/amp) is unsupported. AMP is not available when FedCM is enabled.\n\n2022-04-12\n----------\n\n- [Upgraded One Tap UX on ITP browsers](/identity/gsi/web/guides/features#upgraded_ux_on_itp_browsers) is supported.\n\n2021-4-13\n---------\n\n- [Sign In With Google button](/identity/gsi/web/guides/personalized-button) is supported.\n\n2021-03-17\n----------\n\n- [Accelerated Mobile Pages](/identity/gsi/web/amp/amp) is supported.\n\n2020-3-24\n---------\n\n- [Exponential Cool Down](/identity/gsi/web/guides/features#exponential_cool_down) is supported."]]