Originally submitted by Nat (Nat Sakimura) on 2025-05-23
As I understand, FedCM could be another binding for OpenID Connect.
Account Endpoint looks quite similar to UserInfo Endpoint.
ID assertion endpoint looks quite similar to Token Endpoint.
Of course, there are a bunch of differences but there are similarities as well. For example, scope can also be sent, fields is used instead of claims, token that is returned could be ID Token. etc. There is no client credentials either.
Has any of you contemplated on it?
Google apparently migrated much of Sign in with Google to FedCM and Firefox is also implementing it.
Bitbucket status: new
Bitbucket origin: issue 2179
As I understand, FedCM could be another binding for OpenID Connect.
Account Endpoint looks quite similar to UserInfo Endpoint.
ID assertion endpoint looks quite similar to Token Endpoint.
Of course, there are a bunch of differences but there are similarities as well. For example, scope can also be sent,
fieldsis used instead ofclaims,tokenthat is returned could be ID Token. etc. There is no client credentials either.Has any of you contemplated on it?
Google apparently migrated much of Sign in with Google to FedCM and Firefox is also implementing it.
Bitbucket status: new
Bitbucket origin: issue 2179