Submit FAPI 2.0 MS IANA registrations
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by panva (Filip Skokan) on 2025-11-04
Filing this issue to track a TODO following the recently approved FAPI 2.0 Message Signing Final Specification.
Much like #715 (JARM Errata) we need to submit the request for registration of the response_modes client metadata to the OAuth Dynamic Client Registration Metadata registry.
Bitbucket status: open
Bitbucket origin: issue 844
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
Start by reading the FAPI 2.0 Message Signing Final Specification's IANA Considerations and the OAuth Dynamic Client Registration Metadata registry. Confirm the required registration details for the response_modes client metadata, then follow the IANA submission process. Done means the registration request has been submitted and its status is recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100