#893: FedCM API extension: Error API, AccountAutoSelectedFlag, HostedDomain and Revocation API

Visit on Github.

Opened Sep 5, 2023

こんにちは TAG-さん!

I'm requesting a TAG review of Error API, AccountAutoSelectedFlag, HostedDomain and Revocation API. These are small additions to the existing FedCM API so I'm requesting a single review for all of them together.

  • Summary - With the Error API, the browser can inform users with proper error messages when their sign-in request has failed. - With the AccountAutoSelected Flag API, the browser could help developers to determine if FedCM token requests were initiated with explicit user permission to improve their services. - With the Hosted Domain API, RP can choose to only show the accounts which are associated with a certain domain. - With the Revocation API, developers can revoke the connection between RP and IdP upon user request and update the browser to optimize the future flows.

  • Explainer¹ (minimally containing user needs and example code): (We publish explainers as issues per request from Mozilla. See more context here). For explainers please see the first and second comments of Error API, AccountAutoSelectedFlag, HostedDomain and Revocation.

  • Security and Privacy self-review²: Please see the security and privacy consideration section in the explainers.

  • GitHub repo (if you prefer feedback filed there): [url]

  • Primary contacts (and their relationship to the specification):

    • Yi Gu (@yi-gu, Google Chrome)
    • Nicolas Pena Moreno (@npm1, Google Chrome)
    • Sam Goto (@samuelgoto, Google Chrome, spec editor)

  • Organization/project driving the design: Google Chrome

  • External status/issue trackers for this feature (publicly visible, e.g. Chrome Status):

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • The group where the incubation/design work on this is being done (or is intended to be done in the future): FedID CG
  • The group where standardization of this work is intended to be done ("unknown" if not known): unknown
  • Existing major pieces of multi-stakeholder review or discussion of this design: No
  • Major unresolved issues with or opposition to this design: No
  • This work is being funded by: Google Chrome

You should also know that...

We have spec PRs for Error API and AccountAutoSelectedFlag API since Chrome plans to ship them sooner than the other two.

We'd prefer the TAG provide feedback as

💬 leave review feedback as a comment in this issue and @-notify [@yi-gu, @npm1, @samuelgoto]

Discussions

2023-10-16

Minutes

Hadley: it's 4 features - new additions to the FedCM API... the first 3 I don't think are architectural...

  • when sign-in fails there's no notification - they want to fix - and sounds sensible - maybe we want to ask them if they want to reuse HTTP error codes? but it seems some of the errors are out of scope for http.
  • make it easier for developers to see if you're on the reauthentication pathway - auto-reauth may be unable for reasons only the browser knows... developer might find they're on this pathway - they want to make that more obvious to devs. sounds sensible.
  • for some FedCM instances a relying party might restrict to a particular domain - e.g. a corporate portal for employees of a certain company - they want to make it possible to bake that in. Part of what they are trying to do is make the failure case clearer to the user. Sounds like some of that might be taken care of by the first feature - but thus-far don't think it matters from an arch perspective.
  • allow revocation... when as a user you're signed into a number of IDPs... and you want to revoke one of them - the revocation flow. difficult if you have multiple IDs with a single IDP linked to a given RP...

Peter: So far agree with everything you've said...

Hadley: will let them know none of the changes seem architectural and we will close.

agreed resolution satisfied

Peter: I agree - there are a number of small issues with FedCM but in general seems they are doing a good job.