FedCM Binding of OIDC?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 3
- Avg merge
- 20h 14m
- Merged PRs (30d)
- 1
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by reviewing the stated similarities between FedCM and OpenID Connect, including the Account, UserInfo, ID assertion, and Token endpoints. Done would require an agreed scope and design for whether and how FedCM should bind to OIDC.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100