detecting inconsistent .well-known/openid-configuration vs .well-known/oauth-authorization-server on conformance tests
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Vaguely related to https://github.com/openid/fapi/issues/862
It's suggest that the conformance test could fetch the version it's not currently using (so if it's using openid-configuration, also fetch oauth-authorization-server) and raise a warning if the contents are different, suggesting that (as the keys in the document trace back to the same IANA registry) the contents should be consistent and that interoperability / race conditions might occur if they differ.
If the fetch of the other location fails (e.g. 404) that would be ignored (unless #862 comes to a different conclusion).
An opinion from the working group on whether this is a good idea to check would be appreciated.
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 locating the conformance test that fetches either .well-known/openid-configuration or .well-known/oauth-authorization-server, and review the related decision in issue #862. Done means checking the alternate location when available, warning when both documents differ, and ignoring an unavailable alternate endpoint.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, authorization, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100