Skip to content

Fix: Attach Authorization Token Only When Available #14143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
pavinthan wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix: Attach Authorization Token Only When Available #14143

pavinthan wants to merge 1 commit into from
+5 −6

Conversation

@pavinthan
Copy link

@pavinthan pavinthan commented Jan 15, 2025 •
edited
Loading

Attach the Authorization header only when a token is available, preventing app-level header attachment issues with multiple client configurations.

Description of how you validated changes

  1. Configure multiple Amplify clients within a single app
  2. Make requests from different clients
  3. Encounter the error: NoValidAuthTokens

Checklist

  • PR description included
  • yarn test passes
  • Unit Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

  • Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
  • New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
@pavinthan pavinthan requested a review from a team as a code owner January 15, 2025 04:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant

@pavinthan