Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: codegen token must use base64url encoding #726

Merged
merged 1 commit into from
Sep 12, 2023
Merged

fix: codegen token must use base64url encoding #726

merged 1 commit into from
Sep 12, 2023

Conversation

yordis
Copy link
Member

@yordis yordis commented Sep 12, 2023

closes #718

The "k" (key value) parameter contains the value of the symmetric (or
other single-valued) key. It is represented as the base64url
encoding of the octet sequence containing the key value.

https://www.rfc-editor.org/rfc/rfc7518.html#section-6.4.1

@yordis yordis marked this pull request as ready for review September 12, 2023 02:56
@yordis yordis requested a review from a team as a code owner September 12, 2023 02:56
@yordis yordis merged commit cc125fe into master Sep 12, 2023
2 checks passed
@yordis yordis deleted the fix-718 branch September 12, 2023 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Generating a JWT with kty=oct can fail because of incorrect Base64 encoding
1 participant