Removing padding from url invitations #3238
Merged
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.
I didn't understand this for a while but looking at the RFC PR, I think this is all that's needed.
Uses the common util in the wallet directory to remove the padding from the url via the
bytes_to_b64
function. Then this same util module is used withb64_to_bytes
which pads the invitation string when one is received. This was already in place, meaning that aca-py already handled unpadded invitation urls.This util is used in several other places, mostly for attachment and jws signing. They all remove padding as well. The only place it looks to be used with padding is for bbs_bls_signature proof values. I'm not sure if this is required or not.
NOTE: I changed it for the old connection invitation endpoint as well even though is depreciated and didn't get update in the RFC.