Update some things for v6
This commit is contained in:
parent
da0f01a64f
commit
0ccb61eea5
|
@ -4,6 +4,7 @@
|
|||
|
||||
- Update Ring to 0.14
|
||||
- Remove `iat` check to match the JWT spec
|
||||
- Add ES256 and ES384 signing decoding
|
||||
|
||||
## 5.0.1 (2018-09-10)
|
||||
|
||||
|
|
|
@ -14,6 +14,6 @@ serde_json = "1.0"
|
|||
serde_derive = "1.0"
|
||||
serde = "1.0"
|
||||
ring = "0.14.4"
|
||||
base64 = "0.9"
|
||||
base64 = "0.10"
|
||||
untrusted = "0.6"
|
||||
chrono = "0.4"
|
||||
|
|
11
README.md
11
README.md
|
@ -13,6 +13,15 @@ serde_derive = "1"
|
|||
serde = "1"
|
||||
```
|
||||
|
||||
## Help wanted for v7
|
||||
|
||||
v6 was released as a stopgap version to update Ring and add a couple of features like ES256/384.
|
||||
The results are not very ergonomic once we factor in all the possible ways to load a RSA key for example.
|
||||
A possible solution is to have decoder types as described in https://github.com/Keats/jsonwebtoken/issues/76
|
||||
but I currently do not have the time to implement it myself.
|
||||
I will take any better idea as well of course!
|
||||
|
||||
|
||||
## How to use
|
||||
Complete examples are available in the examples directory: a basic one and one with a custom header.
|
||||
|
||||
|
@ -106,6 +115,8 @@ This library currently supports the following:
|
|||
- RS256
|
||||
- RS384
|
||||
- RS512
|
||||
- ES256
|
||||
- ES384
|
||||
|
||||
### RSA
|
||||
`jsonwebtoken` can only read DER encoded keys currently. If you have openssl installed,
|
||||
|
|
Loading…
Reference in New Issue