Rename claim key for API response MLE handling#194
Open
kiranirabatti wants to merge 1 commit intoCyberSource:masterfrom
Open
Rename claim key for API response MLE handling#194kiranirabatti wants to merge 1 commit intoCyberSource:masterfrom
kiranirabatti wants to merge 1 commit intoCyberSource:masterfrom
Conversation
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.
The JWT token generated for Response MLE includes the claim name "v-c-response-mle-kid" but the CyberSource server expects "v-c-api-response-mle-kid". This mismatch causes the server to reset the connection (ECONNRESET) on POST requests when Response MLE is enabled.
File: src/authentication/jwt/JWTSigToken.js (line 80)
Change: "v-c-response-mle-kid" → "v-c-api-response-mle-kid"
Without this fix, any merchant enabling Response MLE with the Node SDK v0.0.76 will get ECONNRESET on all POST/PUT/PATCH requests (payments, refunds, etc). GET requests are unaffected as they don't include this claim.
Tested and confirmed working with:
PaymentsApi.createPayment (POST /pts/v2/payments)
MicroformIntegrationApi.generateCaptureContext (POST /microform/v2/sessions)
CustomerPaymentInstrumentApi.getCustomerPaymentInstrumentsList (GET)