Use correct Base64 dialect when manually parsing JWTs
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 <c47259303e57c4c1ceb51e5b87b4d1fba755c14a@gmail.com>

credentials/irmago