FedCM multiple IDP support

[npm1]

Session description

We would like to brainstorm ideas to solve the following problem: the FedCM API allows users to login to websites via some identity provider (IDP). Currently the API only allows the developer to specify a single IDP, and we are working on allowing multiple to be specified. It will be fairly easy to allow multiple IDPs in a single JavaScript call, but this has an issue. When there are multiple totally independent providers, we want each IDP to specify their desire to be included in FedCM independently. This allows the website to embed independent IDP SDKs into their site but still allow these IDPs to be shown in an aggregated browser dialog. The challenge is how to achieve this in a reasonable way. There are some brainstormed solutions here but we'd love to further discuss this in a session.

Session goal

Brainstorm ideas to tackle the problem of allowing multiple independent IDPs

Session type

Breakout (Default)

Additional session chairs (Optional)

No response

IRC channel (Optional)

#fedcm-idp

Other sessions where we should avoid scheduling conflicts (Optional)

w3c-fedid/FedCM#7

Instructions for meeting planners (Optional)

No response

Agenda (link or inline) (Optional)

No response

Link to calendar (Optional)

Calendar entry

Meeting materials (Optional)

• Minutes: TBD
• Recording

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

[npm1]

Session Summary:

During this session, we explained why we want to enable multiple FedCM get calls to show up in the same browser UI. We explored some ideas we've thought about, such as dynamic UI and IDP registration. We discussed the importance of letting RPs specify their preference for which IDPs to surface more and the importance of surfacing prominently the accounts that the user has previously used with FedCM in a given RP.

The conversation will continue in the issue: https://github.com/fedidcg/FedCM/issues/319.