Intent to Prototype: FedCM IdP Registration API
Nicolás Peña Moreno
go...@google.com, n...@google.com
Explainer
https://github.com/w3c-fedid/idp-registration
Specification
None
Summary
A proposal to extend FedCM to allow RPs to ask for "any" registered IdP, as opposed to (or, in addition to) enumerating them.
Blink component
Motivation
https://github.com/w3c-fedid/idp-registration?tab=readme-ov-file#the-problem
Initial public proposal
https://github.com/w3c-fedid/idp-registration
TAG review
https://github.com/w3ctag/design-reviews/issues/974
TAG review status
Done
Risks
Interoperability and Compatibility
We introduced a mechanism that allows developers to test the availability of this feature, so websites can make backwards compatible calls.
Gecko: No signal. Will ask for positions after some prototyping.
WebKit: No signal. Will ask for positions after some prototyping.
Web developers: Positive. We have heard extensively from web developers that this is a meaningful addition to the web in this thread: https://github.com/w3c-fedid/idp-registration/issues/2.
Other signals:
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?
None
Debuggability
We added some console.log() messages on failure cases. More to come as we move along.
Is this feature fully tested by web-platform-tests?
Just a few basic ones while we are still learning what’s the right framing for this API:
https://github.com/web-platform-tests/wpt/tree/master/fedcm/fedcm-register
Flag name on about://flags
#fedcm-idp-registration
Finch feature name
FedCmIdPregistration
Non-finch justification
None
Requires code in //chrome?
True
Estimated milestones
No milestones specified
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5111031684399104?gate=6233929744646144
This intent message was generated by Chrome Platform Status.