FedCM API extension: Error API, AccountAutoSelectedFlag, HostedDomain and Revocation API #893
Closed
1 task done
Labels
Resolution: satisfied
The TAG is satisfied with this design
Review type: CG early review
An early review of general direction from a Community Group
Review type: small delta
Topic: identity & credentials
Venue: Federated ID CG
Milestone
こんにちは 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):
Organization/project driving the design: Google Chrome
External status/issue trackers for this feature (publicly visible, e.g. Chrome Status):
Further details:
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]
The text was updated successfully, but these errors were encountered: