test(payments): re-enable bearer token integ tests (AgentCredentialProviderService fixed)#502
Merged
Merged
Conversation
jariy17
approved these changes
Jun 2, 2026
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.
Summary
Reverts #499, which added
@pytest.mark.skipto three bearer-token (CUSTOM_JWT) integration tests while the AgentCredentialProviderService was returning 500s:TestPaymentManagerBearerTokenAuth::test_bearer_token_real_api_callTestPaymentManagerBearerTokenAuth::test_token_provider_real_api_callTestPaymentManagerBearerTokenAuth::test_bearer_create_session_real_api_callThe underlying service issue is now resolved, so the skips are no longer needed.
Why it's safe to re-enable
The original failure was a service-side defect, not a test or SDK bug:
CreatePaymentSession/ListPaymentInstrumentswith a valid Cognito bearer token against a READY CUSTOM_JWT Payment Manager returnedInternalServerException: AgentCredentialProviderServiceException(the post-validation JWT→workload-identity exchange was 5xx-ing). It was reproducible across two independent accounts in us-west-2 and began ~May 29.Verification that it's fixed:
paymentSessionId, with the service correctly derivinguserIdfrom the JWT claim.Secure Integration testruns onmainpass, including the payments job, with no code changes.Change
Pure revert of #499 — removes the three
@pytest.mark.skipdecorators. No other changes.