fix(sdk,mcp,fastmcp): preserve issuer identity, serve PRM verbatim, raise mcp floor past PYSEC-2026-3483 - #23
Open
RobertoIskandarani wants to merge 1 commit into
Open
Conversation
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
…aise mcp floor past PYSEC-2026-3483 - authplane-sdk: issuer identifiers are stored and compared byte-for-byte (RFC 9068 iss, RFC 8414 §3.3) — no trailing-slash stripping on storage or comparison; query- or fragment-bearing issuers are rejected at AuthplaneClient.create() (RFC 8414 §2). Well-known derivation still strips the terminating slash (RFC 8414/9728 §3.1); build_prm_url keeps the resource query and rejects fragment-bearing resources (RFC 8707 §2). - authplane-mcp, authplane-fastmcp: the served Protected Resource Metadata advertises the configured issuer and resource byte-for-byte instead of the AnyHttpUrl-normalised form (RFC 8414/9728 §3.3). - authplane-mcp: mcp floor raised to >=1.28.1,<2 (PYSEC-2026-3483); the elicitation-id field name is resolved from the model schema instead of being hard-coded. authplane-fastmcp declares the same direct floor. - ci: single-source the conformance catalog pin in .conformance-catalog-ref (40-hex guarded) and add a scheduled drift check; pin ruff to >=0.16,<0.17 so formatting stays stable.
RobertoIskandarani
force-pushed
the
fix/issuer-identity-prm-verbatim
branch
from
August 5, 2026 11:49
dc419e7 to
74c48e9
Compare
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
2 participants
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.
What
Three related identifier-handling and dependency fixes, plus CI hardening:
iss, RFC 8414 §3.3). The configured issuer is no longer trailing-slash-stripped before storage, and the AS-metadata issuer comparison no longer strips either side. An issuer carrying a query or fragment component (RFC 8414 §2 forbids both) is rejected atAuthplaneClient.create()with a clearValueErrorinstead of being silently stripped..well-knownURL derivation still drops the terminating slash — that is derivation (RFC 8414/9728 §3.1), not identity.build_prm_urlnow preserves the resource's query component and rejects fragment-bearing resources (RFC 8707 §2).pydantic.AnyHttpUrlfields, which normalise an empty-path authority to a trailing-slash form; clients following the advertised value literally were then rejected by the strict §3.3 comparison. The served document is rewritten soauthorization_serversandresourcematch the configured strings exactly.mcpfloor raised to>=1.28.1,<2(from>=1.23.0,<1.28.0), clearing PYSEC-2026-3483 (affectsmcp <=1.28.0).authplane-fastmcpdeclares the same direct floor since it importsmcpdirectly. The adapter resolves the URL-elicitation id field from the model's own schema instead of hard-coding the camelCase spelling..conformance-catalog-ref(40-hex guarded), with a scheduled drift workflow against the catalog tip;ruffis pinned to>=0.16,<0.17.Breaking (pre-1.0 → next minor)
authplane-mcp: supportedmcprange is now>=1.28.1,<2. Migration: upgrademcpto at least 1.28.1; mcp 2.0 is not yet supported.Verification
develop): PRM served verbatim, RFC 9728 challenge, authenticated MCPinitialize+tools/call, 401 on garbage tokens.