[w3ctag/design-reviews] FedCM: LoginHint, UserInfo, and RPContext (Issue #839)

こんにちは TAG-さん!

I'm requesting a TAG review of LoginHint, UserInfo, and RPContext. These are small additions to the FedCM API, so I'm filing a review to cover all three.

* With LoginHint, the RP can specify a hint about the user account they want displayed in the FedCM UI. Accounts which do not match the hint are not displayed. This is mainly used to provide a better UX for returning users.

* The UserInfo extension allows the IDP to personalize the login experience for returning users, for instance via personalized buttons. After the user has used FedCM with a given IDP on some RP site, this API provides some information about the user accounts to the IDP on subsequent visits to the RP.

* With the context parameter, the IDP can request for the FedCM dialog to show a different title than “Sign in”, to improve the message being displayed to the user in the FedCM UI.

  - Explainers¹ (minimally containing user needs and example code): we publish explainers as issues per request from Mozilla. See the first and second comments of https://github.com/fedidcg/FedCM/issues/382 https://github.com/fedidcg/FedCM/issues/426 https://github.com/fedidcg/FedCM/issues/456
  - Security and Privacy self-review²: [url](https://docs.google.com/document/d/1Ik36ddL_Z3cBd8f6HSPr0WoD2p-7Vg2-Q0pf5wzK0Ns/edit#heading=h.rju99ti8jkvh)
  - GitHub repo (if you prefer feedback filed there): [url](https://github.com/fedidcg/FedCM)
  - Primary contacts (and their relationship to the specification):
      - Nicolas Pena Moreno (@npm1, Google Chrome)
      - Sam Goto (@samuelgoto, Google Chrome)
  - Organization/project driving the design: Google Chrome
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5166718178033664

Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/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: N/A
  - Major unresolved issues with or opposition to this design: N/A
  - This work is being funded by: Google Chrome

You should also know that our current goal is to ship on Chrome 116, which branches on June 20, 2023. I plan to send a PR to the FedCM repo shortly.

We'd prefer the TAG provide feedback as (please delete all but the desired option):
  💬 leave review feedback as a **comment in this issue** and @-notify @npm1

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/839
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/839@github.com>