Conversation
Using `chrono`'s `serde` feature uses ISO 8601 instead of a Unix timestamp as specified in RFC 7519 section 2, "NumericDate". This example uses custom de/serialize functions as shown in the [serde.rs example, "Custom Date Format"](https://serde.rs/custom-date-format.html). NOTE: Currently fractional values are not supported in the example, though they are in the spec.
Clarify Key formats
As specified in https://tools.ietf.org/html/rfc7518#section-3.5 - PS256 - RSASSA-PSS using SHA-256 hash algorithm - PS384 - RSASSA-PSS using SHA-384 hash algorithm - PS512 - RSASSA-PSS using SHA-512 hash algorithm
Add example of using `chrono::DateTime` in claims
|
Could |
|
It will |
|
There’s been no activity from Keats since this last message, can a PR be forked to just include the ring bump? |
It should be 0.16.5 now. |
|
I will take 30 minutes to try to update this to ring 0.16.5. |
|
You can merge #96 into the next branch to update this PR to use ring 0.16.5. Thanks for all your work on jsonwebtoken. I am planning to submit some more PRs soon to help you out. |
Use *ring* 0.16.5.
Add PEM decoding support (#106)
|
An alpha version has been released: https://docs.rs/jsonwebtoken/7.0.0-alpha.1/jsonwebtoken/index.html If anyone has some time to try it and give feedback it would be great. The main change is that the encode/decode functions now take the .pem instead of the der format, it can decode using RSA pub key components and adds RSA PSS. |
Add EncodingKey & DecodingKey
No description provided.