[w3ctag/design-reviews] Early Design Review: Lightweight FedCM (Issue #986)

こんにちは TAG-さん!

I'm requesting a TAG review of Lightweight FedCM.

The goal of this project is to provide a purpose-built API for enabling  secure and user-mediated access to cross-site top-level unpartitioned  cookies. This is accomplished with integration with the [Credential Management API](https://w3c.github.io/webappsec-credential-management/) to enable easy integration with alternative authentication mechanisms. A site that wants a user to log in calls the `navigator.credentials.get()` function with arguments defined in this spec the browser ensures there  is appropriate user mediation and identity provider opt-in and hands off a token. With those assurances, the browser may also decide there is no  additional privacy loss associated with access to unpartitioned state,  and choose to automatically grant access to Storage Access requests.

  - Explainer¹ (minimally containing user needs and example code): https://github.com/fedidcg/LightweightFedCM/blob/main/README.md
  - User research: None
  - Security and Privacy self-review²: https://github.com/fedidcg/LightweightFedCM/blob/main/security-privacy-self-review.md
  - GitHub repo: https://github.com/fedidcg/LightweightFedCM
  - Primary contacts (and their relationship to the specification):
      - Benjamin VanderSloot (@bvandersloot-mozilla), Mozilla, Author
      - Johann Hofmann (@johannhof), Google, Author
      - Heather Flanagan (@hlflanagan), Spherical Cow Consulting, LLC, Community Group Chair
  - Organization/project driving the design: Mozilla
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): 
      - [Bugzilla: [meta] Lightweight FedCM Implementation](https://bugzilla.mozilla.org/show_bug.cgi?id=lightweight-fedcm)


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): [Federated Identity CG](https://fedidcg.github.io/)
  - The group where standardization of this work is intended to be done ("unknown" if not known): [Federated Identity WG](https://www.w3.org/groups/wg/fedid/)
  - Existing major pieces of multi-implementer review or discussion of this design: 
    - Substantial discussions from FedIDCG meetings:
      - https://github.com/fedidcg/meetings/blob/38e2079ee17f2cd045293551a64b4426296375c3/2024/2024-05-14-notes.md?plain=1#L140-L233
      - https://github.com/fedidcg/meetings/blob/38e2079ee17f2cd045293551a64b4426296375c3/2024/2024-06-11-notes.md?plain=1#L70-L221
      - https://github.com/fedidcg/meetings/blob/38e2079ee17f2cd045293551a64b4426296375c3/2024/2024-08-06-notes.md?plain=1#L39-L119
      - https://github.com/fedidcg/meetings/blob/38e2079ee17f2cd045293551a64b4426296375c3/2024/2024-08-20-notes.md?plain=1#L41-L226

  - Major unresolved issues with or opposition to this design:
    - The only major open point of contention among implementers is how to handle privacy protections on the navigation this API may induce. This reduces to whether this proposal should be held to a higher privacy standard than `window.open` by its design or if it should just accept any general navigational tracking mitigations that may come in the future. 

  - This work is being funded by: Mozilla and Google


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

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