Add JSON-based setup option to authorization server conformance test
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- authorization, testing
Research direction
Start from the authorization conformance-test command and its existing command-option handling. Add the JSON setup option with command options taking precedence over JSON values and defaults, and preserve errors when required authorization-server settings are absent; verify the three example invocation cases.
Written by the indexing model from the issue text.
Description
Background
In the future, conformance test for authorization server requires many options such as url, client_id, client_secret, redirect_uri.
Solution
Conformance test for authorization server provides the following setup options so that testers can choose their preferred setup option. The number is priority of the options. However, options unrelated to the authorization server, such as outputDir and specVersion, are not covered from these setup options.
- command options
- json file option
- default value
For Example
In the following case, http://auth1.example.com, which is set in url option, will be used.
npx @modelcontextprotocol/conformance authorization --file autorization-server-settings.json --url http://auth1.example.com
In the following case, http://auth2.example.com, which is set in autorization-server-settings.json, will be used.
npx @modelcontextprotocol/conformance authorization --file autorization-server-settings.json
autorization-server-settings.json
{
"url": "http://auth2.example.com"
}
In the following case, conformance test for authorization server occures error.
npx @modelcontextprotocol/conformance authorization
- Dominant language
- TypeScript
- Stars
- 127
- Forks
- 101
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 6
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.
More from modelcontextprotocol/conformance
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/conformance#315 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/conformance#312 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
All issues in modelcontextprotocol/conformance
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·