fix: serialize opaque as a credential string#388
Merged
brendanjryan merged 3 commits intowevm:mainfrom Apr 23, 2026
Merged
Conversation
commit: |
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.
Summary
challenge.opaquein credentials as the spec-compliant base64url string shapeopaquecredentialsAGENTS.mdto matchpaymentauth.orgThis bug could result in clients like tempo-wallet rejecting opaques from mppx servers, due to missing base64 decoding
Root cause
Challenge.serialize()already encodedopaquecorrectly forWWW-Authenticate, butCredential.serialize()spread the in-memory challenge object directly into the credential JSON and only re-encodedrequest. That mademppxemitopaqueas an expanded object in credentials, while the Payment auth spec requires the echoedchallenge.opaquefield to remain a base64url string.