meaning of FAPI2 requirements around publishing discovery data
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
What does the 'and' here mean:
shall distribute discovery metadata (such as the authorization endpoint) via the metadata document as specified in [OIDD] and [RFC8414];
Does it mean a server has to publish both?
Currently the conformance tests check:
- if openid connect is enabled, only openid-configuration is checked
- if openid connect is not enabled, only oauth-authorization-server is checked
Given the 'and' I'm not actually sure this is correct and if server's are expected to publish in both locations?
Discussed a bit on today's WG call.
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 comparing the quoted FAPI2 requirement with the OIDD and RFC8414 references, then inspect the conformance tests described in the issue: OpenID configuration is checked when OIDC is enabled, and OAuth authorization-server metadata otherwise. Done means the WG clarifies whether both metadata documents are required and the tests reflect that decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100