Google은 개발자로부터 FedCM 자동 로그인 흐름 사용자 동작 요구사항에 관한 응답을 받았습니다. 개인 정보 보호를 강화하기 위해 Chrome에서는 FedCM 출시 전에 사용자가 웹사이트를 승인했더라도 각 Chrome 인스턴스에서 Google 계정으로 웹사이트에 로그인할지 다시 확인해야 합니다. 이 일회성 재확인은 원탭 메시지를 한 번 클릭하여 사용자의 로그인 의도를 나타내는 방식으로 이루어집니다. 이 변경사항으로 인해 일부 웹사이트의 자동 로그인 전환율이 초기에 중단될 수 있습니다.
최근 M121에서 Chrome은 FedCM 자동 로그인 흐름 UX를 변경했습니다. 재확인은 서드 파티 쿠키가 제한된 경우에만 필요합니다. 이는 다음을 의미합니다.
서드 파티 쿠키 제한이 100% 적용되기 전(최신 일정은 개인 정보 보호 샌드박스 뉴스 및 업데이트 페이지 참고)에는 FedCM 자동 로그인 시 재방문자에게 재확인이 필요하지 않습니다.
사용자가 FedCM UI로 재확인하면 이 재확인이 사용자 동작 요구사항에 반영됩니다.
FedCM 자동 로그인은 현재 사용자가 서드 파티 쿠키를 수동으로 제한했거나 향후 Chrome에서 기본적으로 제한할 때 확인 상태를 확인합니다.
이번 변경사항으로 인해 자동 로그인 전환율이 중단되지 않도록 모든 자동 로그인 개발자는 최대한 빨리 FedCM으로 이전하는 것이 좋습니다.
자동 로그인 흐름의 경우 웹사이트에서 FedCM을 선택하더라도 이전 Chrome (M121 이전)에서는 GIS JavaScript가 FedCM을 트리거하지 않습니다.
2023-08-15
Federated Credential Management API (FedCM)에 대한 지원을 추가했습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-03-17(UTC)"],[[["\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."]]
