Repository navigation
Conversation
The catalog OAuth form required authorization and token URLs even though registration discovers both from the issuer. Make empty values valid while still rejecting malformed non-empty URLs. Add a regression that submits empty endpoints for discovery. Ref #7464 Signed-off-by: Li Fengmin <2080291162@qq.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes IBM/mcp-context-forge#7464
Catalog registration discovers the authorization and token endpoints from the issuer, so requiring both fields blocked entries without published metadata. Empty values are now accepted; non-empty values still require http(s) URLs. Issuer, scopes, and client credentials remain required.
Validation:
vitestCatalogOAuthForm + ServerCatalog: 98 passednpm run typecheck