Use correct Base64 dialect when manually parsing JWTs
JWTs use URL-encoded base64 (with - _ instead of + /). This fixes parsing bugs
that would occur when issuing attributes containing certain non-alphanumeric
characters like ~.
Fixes #24.
Co-authored-by:
Koen van Ingen <koenvaningen@gmail.com>
Please register or sign in to comment