feat: implement inbound auth#467
Draft
aidandaly24 wants to merge 15 commits intoaws:feat/gateway-integrationfrom
Draft
feat: implement inbound auth#467aidandaly24 wants to merge 15 commits intoaws:feat/gateway-integrationfrom
aidandaly24 wants to merge 15 commits intoaws:feat/gateway-integrationfrom
Conversation
…angChain, OpenAI, Google ADK)
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.
Description
Add CUSTOM_JWT inbound authentication support for gateways. When creating a gateway with CUSTOM_JWT authorizer, the CLI now collects the full JWT configuration including allowed scopes and
agent OAuth credentials, auto-creates a managed OAuth credential for the agent, and wires Bearer token authentication into all agent framework templates.
Gateway wizard extension: The CUSTOM_JWT configuration flow now collects:
Managed credential auto-creation: When a CUSTOM_JWT gateway is created, the CLI automatically creates a managed OAuth credential ({gateway-name}-agent-oauth) so the agent can authenticate to
the gateway. Managed credentials are protected from accidental deletion (requires --force).
Agent template Bearer token auth: All four agent framework templates (Strands, LangChain, OpenAI, Google ADK) now support Bearer token authentication via OAuth client credentials flow with
token caching and automatic refresh.
CLI flags: Added non-interactive support with --allowed-scopes, --agent-client-id, and --agent-client-secret flags for agentcore add gateway.
UX fix: Gateway discovery URL input now uses placeholder text instead of pre-populated https:// that interfered with pasting.
Depends on #417 (outbound auth / identity OAuth support).
Related Issue
N/A
Documentation PR
N/A
Type of Change
Testing
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.