Contextualize account selection

[kajohnston]

Some users have numerous accounts with an identity provider. For these users, it's beneficial for the account selection UI to provide contextual information on the account beyond.

For example, users frequently have numerous Google accounts, when signing into a YouTube embed they may not remember which account they predominantly use on the YouTube service. User's would benefit from contextual signals, for example how many "channel subscriptions" they have on each Google account, or even just a "recently active on YouTube" indication.

In this case, the Identity provider (Google) could determine what account signals it will support (# channels subscribed to), and the embed app (YouTube) could specify which account signals are relevant to the given user context.

[npm1]

Interesting feature request! One key requirement for the FedCM API is that when the IDP is returning the accounts list, it should not have awareness about the RP that the user is interacting with. Thus the way I could see of achieving this would be to have to append the information in all of the account responses from the IDP, and have the RP request that this additional metadata be displayed in certain cases.

For 'recently active', the user agent should also have some knowledge about that which it could in theory use to order the accounts being displayed to the user so that the user is more likely to pick the account which was recently used.

[Bojhan]

We currently use recency as the primary ordering mechanism in Seamless Access (where we allow multiple IDP's). It seems to work quite well, just slightly harder when your switching a lot.