f4746a7306
- The jwt token was declared as using HS256 as algorithm, but was using HS512. - No need to base64-encode then remove the padding when we can simply encode without padding. - Factorize the header+payload concatenation as data Odds are that this integration was broken from the start (HS512 vs HS256), so I'm not sure if it's better to add tests or to simply get rid of it. |
||
---|---|---|
.. | ||
shaarli.go |