OpenID Federation client id prefix does not allow ephemeral encryption keys
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
The openid_federation client id prefix mentions:
The client_metadata parameter, if present in the Authorization Request, MUST be ignored when this Client Identifier Prefix is used
This however feels a bit too strict, since it removes the possibility to use ephemeral encryption keys.
Is it intentional that ephemeral encryption keys are not supported for openid_federation client id prefix? Is this something that cannot be changed anymore and should be clarified in profiles?
Contributor guide
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
Start by reviewing the OpenID Federation client id prefix rule quoted in the issue, especially the requirement to ignore client_metadata in the Authorization Request. Determine whether that rule intentionally excludes ephemeral encryption keys and whether the intended clarification belongs in the relevant profiles. Done means the expected behavior and specification location are resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100