3 ms·
One thing missing: the "cryptographic signature" isn't required to be a cryptographic signature by the standard. You need to ensure, by configuration or by libr
by falcolas 7y ago
One thing missing: the "cryptographic signature" isn't required to be a cryptographic signature by the standard. You need to ensure, by configuration or by library defaults, that the algorithm of 'none' is not allowed, otherwise someone could freely modify and replay the JWT for all time.
https://tools.ietf.org/html/rfc7519#section-6.1 https://tools.ietf.org/html/rfc7519#section-6.1