-
Since v1.68 we have now ECDSA support also for the account key introduced with fbf9782cbf180031f32abb559bf092c38b8202a9
But somehow it doesn´t really work.
Because there is no option yet to tell gets…
-
-
I didn't notice another issue on this so I thought I'd mention it. Could be that I've mucked something up, could be coming from a lib you're using, or could be coming from you guys. Not sure so I thou…
-
In the [Supported Features section](https://github.com/jwtk/jjwt/blob/master/README.md#specification-compliant) of the README, the NIST `P-521` curve is misnamed as `P-512` in the `ES512` JWS algorith…
-
We are currently trying to use jjwt to validate ES512 tokens, but this doesn't work correctly in version 0.6.0 of jjwt. It does work correctly due to the various ECDSA fixes that have happened in the …
-
```
$ acme reg -gen mailto:some.email@example.com
400 urn:acme:error:malformed: signature type 'RS256' in JWS header is not supported, expected one of RS256, ES256, ES384 or ES512
```
Looks like the …
-
You are using names for algorithms like: `[HmacMD5, HmacSHA1, HmacSHA224, HmacSHA256, HmacSHA384, HmacSHA512]`, and by default you are using `HmacSHA256`.
When I take a token generated by default to …
-
We need to implement client key generator which prepare 2 files:
1) JWKS with public keys to store in LDAP
2) JKS with private keys to use then in client code
3) Utility class to simplify key loading …
yurem updated
8 years ago
-
Only HS256, HS348 and HS512 works in node js.(i'm using node js 6.x)
and RS256, RS348, RS512, ES256, ES348 and ES512 doesn't work.
**the following code is right:**
return jwt.sign({ foo : "bar"}, "M…
-
Upgrading from 1.7.9 to 1.8.0 brings me `erlang error: {:not_supported, ["P-521", :HS512]}`. Does that mean that my tokens were failing silently before or is this a bug with 1.8.0?
Here's the specifi…