LGTM to experiment till M105 (inclusive)

On Monday, March 21, 2022 at 5:06:17 PM UTC+1 Sam Goto wrote:

> Contact emails
>
> g...@google.com 
>
> Explainer
>
> https://github.com/fedidcg/FedCM/blob/main/explainer.md
>
> Specification
>
> https://fedidcg.github.io/FedCM/
>
> Summary
>
> A Web Platform API that allows users to login to websites with their 
> federated accounts in a manner compatible with improvements to browser 
> privacy.
>
> In this origin trial, we are interested in experimenting with an account 
> chooser for federated accounts, which we expect to be a foundational 
> infrastructure for the Web going forward.
>
> Blink component
>
> Blink > Identity > FedCM 
> <https://bugs.chromium.org/p/chromium/issues/list?q=component%3ABlink%3EIdentity%3EFedCM&can=2>
>
> TAG review
>
> Spec review: https://github.com/w3ctag/design-reviews/issues/718 
>
> Early review: https://github.com/w3ctag/design-reviews/issues/622  
>
> TAG review status
>
> Pending
>
> Risks
> Interoperability and Compatibility
>
>                 Zero compatibility risk (new API)
>
> Interoperability risk not yet known, currently working on getting formal 
> signals.
>
> Gecko: No Signals. standards position filed 
> <https://github.com/mozilla/standards-positions/issues/618> 
>
> WebKit: No Signals. standards position filed 
> <https://lists.webkit.org/pipermail/webkit-dev/2022-March/032153.html>
>
> Web developers: No signals. We have been proactively working with Identity 
> Providers and expect much of the origin trial experimentation to be a 
> determining factor on their position.
>
> Other signals: No signals. This API is being developed within the FedID CG 
> with attendance of identity providers, browser vendors and standards 
> experts. We are working on a community report https://github.com/fedidcg.
>
> Activation
>
>   We made a deliberate and concerted effort to make as many backwards 
>
> compatible changes as we possibly could to facilitate the adoption of 
> FedCM. 
>
> When it wasn’t possible, we favored changes impacting Browsers and 
> Identity 
>
> Providers and reduced changes impacting websites and users.
>
>   So far, we think we maintained backwards compatibility with website’s 
> server-
>
> side Infrastructure, which we expect to be a meaningful activation lever.
>
> We believe we found a structure that would make it easy for websites to 
> adopt, but that's one of the risks that we are trying to mitigate as soon 
> as we possibly can as part of the origin trial.
>
> WebView Application Risks
>
> Does this intent deprecate or change behavior of existing APIs, such that 
> it has potentially high risk for Android WebView-based applications?
>
> This API does not deprecate or change behavior of existing APIs.
>
>
> Goals for experimentation
>
> To learn about:
>
>
>    - 
>    
>    requirements: what aspects of federated identity are going to be 
>    affected by phasing out third party cookies?
>    - 
>    
>    demand: who is going to be affected? and how important is it for them?
>    - 
>    
>    deployment viability: is it a practical solution?
>    - 
>    
>    user acceptance: does our implementation perform well with users?
>    
>
> Ongoing technical constraints
>
> The following are current technical constraints that we expect to resolve 
> as we go along (i.e. we are actively working on these known constraints):
>
>
>    - 
>    
>    Android only implementation (here 
>    <https://bugs.chromium.org/p/chromium/issues/detail?id=1296263> is the 
>    desktop implementation tracking bug)
>    - 
>    
>    Only ID tokens provided, no access or refresh tokens (access tokens 
>    <https://github.com/fedidcg/FedCM/pull/208> PR in progress)
>    - 
>    
>    Front-channel logout designed and implemented, but disabled for origin 
>    trials (HOWTO 
>    <https://github.com/fedidcg/FedCM/blob/main/explorations/HOWTO.md> try 
>    it)
>    - 
>    
>    Only available in top level frames 
>    
>
> Debuggability
>
> Basic devtools integration supported. More to come as we learn.
>
> https://github.com/fedidcg/FedCM/blob/main/explorations/HOWTO.md
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1291653
>
>
> Will this feature be supported on all six Blink platforms (Windows, Mac, 
> Linux, Chrome OS, Android, and Android WebView)?
>
> No
>
> We expect the feature to be available on all platforms (Windows, Mac, 
> Linux, ChromeOS and Android) except WebView. The current implementation is 
> currently only supported on Android, with Desktop 
> (Windows/Mac/Linux/ChromeOS) coming before our I2S.
>
> Is this feature fully tested by web-platform-tests 
> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>
> ?
>
> Yes 
> <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/credential-management/fedcm.https.html?q=file:wpt%20fedcm&ss=chromium>
> .
>
> DevTrial instructions
>
> https://github.com/fedidcg/FedCM/blob/main/explorations/HOWTO.md
>
> Flag name
>
>  chrome://flags/#fedcm
>
> Requires code in //chrome?
>
> True
>
> Tracking bug
>
> You can track our progress here:
>
> https://chromium-review.googlesource.com/q/hashtag:FedCM+is:merged
>
> Launch bug
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1216142
>
> Measurement
>
> kFederatedCredentialManagement
>
> Estimated milestones
>
> OriginTrial - Android
>
> 101-105
>
> Origin Trial - Desktop 
>
> 102-105
>
> DevTrial on android
>
> 98
>
> Link to entry on the Chrome Platform Status
>
> https://chromestatus.com/feature/6438627087220736
>
> Links to previous Intent discussions
>
>    - 
>    
>    Intent to prototype 
>    
> <https://groups.google.com/a/chromium.org/g/blink-dev/c/2B4TJ7j2U4M/m/1X5T3OszCAAJ>
>    - 
>    
>    Ready for Trial 
>    <https://groups.google.com/a/chromium.org/g/blink-dev/c/jlV_1m7uUAg>
>    
>
> This intent message was generated by Chrome Platform Status 
> <https://chromestatus.com/>.
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ff7486cd-661c-4c98-8b53-ceab18037e9bn%40chromium.org.

Reply via email to