feat(mcp): Add AuthScheme and IdentityResolver support to HttpMcpProxy#1169
Open
DivyaMaddipudi wants to merge 1 commit intosmithy-lang:mainfrom
Open
feat(mcp): Add AuthScheme and IdentityResolver support to HttpMcpProxy#1169DivyaMaddipudi wants to merge 1 commit intosmithy-lang:mainfrom
DivyaMaddipudi wants to merge 1 commit intosmithy-lang:mainfrom
Conversation
Add proper auth separation to HttpMcpProxy alongside the existing signer() path. The new authScheme() + identityResolver() + signerContext() builder API follows the canonical smithy-java auth architecture (AuthScheme + IdentityResolver + Signer separation) used by ClientPipeline. This enables direct use of SigV4AuthScheme and SdkCredentialsResolver for AWS-authenticated MCP endpoints without needing a custom adapter class. The existing signer() path remains unchanged for backward compatibility.
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
1 participant
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.
Add proper auth separation to HttpMcpProxy alongside the existing signer() path. The new authScheme() + identityResolver() + signerContext() builder API follows the canonical smithy-java auth architecture (AuthScheme + IdentityResolver + Signer separation) used by ClientPipeline. This enables direct use of SigV4AuthScheme and SdkCredentialsResolver for AWS-authenticated MCP endpoints without needing a custom adapter class.
The existing signer() path remains unchanged for backward compatibility.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.