chore: encode nonces as base64url everywhere #353
Closed
+211
−40
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.
Use only URL-safe base64 encoding for nonces, both stored in the session, extracted from the token, and returned to user.
This is a bit tricky since the byte array goes through several marshalling and unmarshalling steps. This change attempts to fix the integration test test_freshness_check_fail which was working correctly with CCA but incorrectly with PSA since the different nonce formats would cause validation failures.
Key Changes
Testing
Fixes #337 (if there's a related issue)
Signed-off-by: GitHub Copilot [email protected]