You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Base64url Encoding
Base64 encoding using the URL- and filename-safe character set
defined in Section 5 of RFC 4648 [RFC4648], with all trailing '='
characters omitted (as permitted by Section 3.2) and without the
inclusion of any line breaks, whitespace, or other additional
characters. Note that the base64url encoding of the empty octet
sequence is the empty string. (See Appendix C for notes on
implementing base64url encoding without padding.)
The text was updated successfully, but these errors were encountered:
nbaars
pushed a commit
to nbaars/keycloak-mock
that referenced
this issue
Jun 26, 2023
When using the mock to interact with a Go library the parsing fails:
The JWKS is as follows:
The
n
however uses a base-64 encoding with a trailing=
which is not allowed according to the spec, see: https://datatracker.ietf.org/doc/html/rfc7515#appendix-C:The text was updated successfully, but these errors were encountered: