The FedCM team says hello to all our newsletter subscribers!
We updated how Chrome’s FedCM UI displays filtered-out accounts.
Clearer communication about filtered-out accounts
Several cases may cause an account to be filtered out and ineligible for login:
A Relying Party (RP) only permits accounts associated with a specific domain (using the domain hint API).
An RP filters out all but returning accounts (using login hint API).
Identity providers (IdPs) can label accounts, allowing RPs to filter them based on the label by specifying the corresponding configURL (using Custom Account Labels).
In Chrome 132 and earlier releases, the FedCM UI didn't display accounts that were filtered out by the RP and IdPs. As a result, when a user logged in with an IdP but no accounts were available to use on this RP, the mismatch UI would be displayed every time.
To enhance the user experience, FedCM is introducing a UI change. Chrome will now show filtered-out accounts in the UI if these conditions apply:
The user has already attempted to sign in to the IdP in a popup and returned to the RP.
All the fetched accounts are filtered out, and there’s no account available for the user to sign into this RP.
This will provide users with an understanding that some accounts, while recognized by FedCM, are not eligible for use on the current RP.
Try it yourself with our domain hint demo.
Key benefits
Reduced confusion: If a user logs into an account that's filtered out, they will see the account listed and understand that it's not accepted by the RP. Before the change, the user could be confused by an infinite loop: they would try to sign in to a filtered-out account and then see the mismatched UI, which prompted them to sign in again.
Contextual information: The UI will take into account the RP context and domain hints to provide relevant guidance to the user.
Example UI
UI showing a filtered out account
We value your feedback
We encourage you to share your thoughts and feedback on this change. You can file an issue on our issue tracker. We will continue to keep the FedCM developer documentation updated.