fix: fail fast when CUSTOM_JWT agent has no bearer token available#817
Merged
aidandaly24 merged 1 commit intomainfrom Apr 13, 2026
Merged
fix: fail fast when CUSTOM_JWT agent has no bearer token available#817aidandaly24 merged 1 commit intomainfrom
aidandaly24 merged 1 commit intomainfrom
Conversation
When an agent is configured for CUSTOM_JWT but no OAuth credentials are stored and no --bearer-token is provided, the CLI silently fell back to SigV4 auth which always fails with a cryptic "Authorization method mismatch" error. Now the CLI returns a clear error message in the non-interactive path, and the TUI shows a warning guiding the user to press T to enter a token manually. Closes #814
Contributor
Package TarballHow to installnpm install https://github.com/aws/agentcore-cli/releases/download/pr-817-tarball/aws-agentcore-0.8.0.tgz |
Contributor
Coverage Report
|
vivdalal
approved these changes
Apr 10, 2026
aidandaly24
added a commit
that referenced
this pull request
Apr 13, 2026
PR #817 changed invoke to fail fast client-side when a CUSTOM_JWT agent is invoked without a bearer token, producing a different error message. The E2E assertions still expected the old server-side "authorization mismatch" pattern, causing two test failures on main.
15 tasks
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
3 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.
Description
When an agent is configured for
CUSTOM_JWTbut no OAuth client credentials are stored (i.e.,--client-idand--client-secretwere not provided duringagentcore add agent),agentcore invokesilently falls back to SigV4 authentication. The runtime rejects SigV4 with a cryptic "Authorization method mismatch" error, giving the user no indication of what went wrong.This PR adds:
src/cli/commands/invoke/action.ts): Returns a clear error when CUSTOM_JWT is configured but no token is available, guiding the user to either provide--bearer-tokenor re-add the agent with--client-idand--client-secret.src/cli/tui/screens/invoke/useInvokeFlow.ts): Shows a warning message when auto-fetch isn't possible, guiding the user to press T to enter a token manually.Related Issue
Closes #814
Documentation PR
N/A
Type of Change
Testing
How have you tested the change?
npm run test:unitandnpm run test:integnpm run typechecknpm run lintsrc/assets/, I rannpm run test:update-snapshotsand committed the updated snapshotsAll pre-existing test failures are unchanged (19 failing test files on main, 19 with this change — identical set).
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.