使用 Google 版本資訊登入
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本頁面列出 Google Identity 服務 JavaScript 程式庫的新功能和重大變更。
2025-03-17
2024-12-01
2023-12-21
Google 身分識別服務的 Federated Credential Management (FedCM) Beta 版已於 2023 年 8 月推出。許多開發人員測試了 API,並提供寶貴的意見回饋。
Google 收到開發人員的回應之一,是關於 FedCM 自動登入流程的使用者手勢要求。為提升隱私權,Chrome 會要求使用者在每個 Chrome 執行個體中,重新確認是否要使用 Google 帳戶登入網站,即使使用者在 FedCM 推出前已核准該網站也一樣。這項一次性的重新確認作業,只要點按一次 One Tap 提示,即可完成,藉此證明使用者有意登入。這項變更可能會導致部分網站的自動登入轉換率初期出現中斷。
近期在 M121 中,Chrome 對 FedCM 自動登入流程的使用者體驗進行了變更。只有在第三方 Cookie 受到限制時,才需要再次確認。因此:
在第三方 Cookie 限制提高至 100% 之前 (如要查看最新時間表,請參閱隱私權沙箱的「新聞和更新」頁面),FedCM 自動登入功能不需要針對回訪使用者重新確認。如果使用者透過 FedCM UI 重新確認,這項重新確認動作就會計入使用者手勢規定。
當使用者今天手動限制第三方 Cookie,或在未來的 Chrome 中預設限制第三方 Cookie 時,FedCM 自動登入功能會檢查確認狀態。
因應這項異動,我們建議所有自動登入功能開發人員盡快改用 FedCM,以減少對自動登入轉換率的影響。
對於自動登入流程,即使網站選擇啟用 FedCM,GIS JavaScript 也不會在舊版 Chrome (M121 之前) 上觸發 FedCM。
2023-08-15
2022-04-12
2021-4-13
2021-03-17
2020-3-24
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-03-17 (世界標準時間)。
[null,null,["上次更新時間: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."]]