Skip to Content
Platform.Ontology

Federated Credential Management (FedCM)

A browser mediated sign in that works without third party cookies or hidden redirects.

Asks you firstSign in and identityFederated loginWeb browsersWhen you are signed in

In one line

Can sign you in with the account you pick in a browser prompt

A browser mediated sign in that works without third party cookies or hidden redirects.

The browser asks the identity provider for account data, shows a prompt, and only after consent shares the ID token with the site. Stops identity providers from tracking silently. Google is moving its sign in to FedCM.

What it can and can't do

What the user does: You tap Sign in with Google (or similar) and choose an account in the browser box

It can

  • Show a browser account picker listing accounts you already have with the sign in provider
  • Receive a sign in token for the one account you choose
  • Sign you in without third party cookies or a pop up window

It cannot

  • Get your account details before you approve in the prompt
  • Work in Firefox or Safari; only Chrome, Edge and Samsung Internet support it
  • Pick an account for you; the prompt always asks first

How it differs between platforms: Chrome, Edge and Samsung Internet support it. Firefox and Safari do not, so sites there fall back to pop ups or redirects.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported1082022-11-29None
EdgeSupported1082022-12-05None
FirefoxNot supportedNot availableNot listedNo public ship found, verify
SafariNot supportedNot availableNot listedNo public ship found, verify
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidSupported1082022-11-29None
Samsung InternetSupported21.02023-05-19None

How a site asks for it

APInavigator.credentials.get({identity: {providers: [...]}})
Permission nameidentity-credentials-get
Permissions policyidentity-credentials-get
Browser compat keysapi.IdentityCredential
How access is grantedprompt
What the user seesBrowser account chooser dialog
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsBrowser remembers sign in state per account; revocable in site settings
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Typical flow

  1. Site calls credentials.get with identity
  2. Browser contacts IdP, shows chooser
  3. Person consents
  4. Site receives token

Data you get

What comes back: ID token after consent
Shape: object
How often: per sign in

No individual data fields. The signal is the access itself.

Technical limits

  • Needs HTTPS and a well known file at the provider
  • Shows browser UI before any data is shared
  • Chrome ships it; other browsers vary

The story

What it is

The browser itself runs a sign in with Google style prompt, so no hidden cookies are needed.

For you

You see a small box from your browser saying something like 'Continue as Sam' with your account picture. It appears before you type anything. You tap once and you are in.

For makers

Sites keep one click social login alive even when browsers block third party cookies. The browser, not the site, controls the prompt, so sign in rates stay high without sneaky redirects.

Where you see it

TypeExampleApps
gamesA browser game portal shows a 'Continue as Sam' box so a player can sign in and load saved progress in one tap, before the game even starts.Poki, CrazyGames
mediaA news site lets a returning reader sign in with Google in one tap so a paywall opens and their saved articles appear.The New York Times
shoppingA store shows the account chooser at checkout so a shopper skips typing an address and card details.None named
productivityA design or notes web app offers a one tap sign in the moment the page loads, so the team can jump straight into a shared board.Figma, Notion
securityA site checks that the sign in came through the browser prompt, which makes fake pop up login pages harder to pass off.None named
adsIdentity providers can no longer quietly learn every site you visit, because the browser asks you first and hides your visit until you agree.None named

Risks

  • Identity provider learns you visited
  • Prompt fatigue

What the platform says

Good uses and abuse

Legitimate uses

  • Third-party-cookie free federated login

Known abuse

  • Identity providers learning relying sites

Scores

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2022-11, Chrome 108: FedCM shipped
  • 2024-06, Chrome 126: Updates: multiple IdP and button mode (verify milestone)

Sources

How well checked: Checked against real behavior.

On this page