QJsonWebToken
QJsonWebToken copied to clipboard
remove README.md Limitations.
- Conform to RFC7519
- Payload value type:
Its value MUST be a number containing a NumericDate value.
in- 4.1.4. "exp" (Expiration Time) Claim
- 4.1.5. "nbf" (Not Before) Claim
- 4.1.6. "iat" (Issued At) Claim
- Payload value type:
- Conform to RFC7515
- Section 2. Terminology / Base64url encoding
- Base64 encoding using the URL- and filename-safe character set defined in Section 5 of RFC 4648 [RFC4648], with all trailing
=
characters omitted (as permitted by Section 3.2) and without the inclusion of any line breaks, whitespace, or other additional characters.
- Base64 encoding using the URL- and filename-safe character set defined in Section 5 of RFC 4648 [RFC4648], with all trailing
- Section 2. Terminology / Base64url encoding
Hi, thanks for the contribution, it seems you removed several limitations, super cool! I will try to test it but I have a couple of questions:
-
Do have a guideline for linking with libqca?
-
Why is the JsonWebKey and whi not use a secret string as in the implementations in https://jwt.io/ ?
Thank you for your contributions !
Juan.
Do have a guideline for linking with libqca?
QCA is here: https://github.com/KDE/qca
And I found QCA building note: https://github.com/JPNaude/dev_notes/wiki/Using-the-Qt-Cryptographic-Architecture-with-Qt5
Important: Don't forget copy the builded lib/qca-qt5/crypto
(only crypto
dir) into Qt plugins directory.
Why is the JsonWebKey and whi not use a secret string as in the implementations in https://jwt.io/ ?
In short using JsonWebKey for support the RSA.
JsonWebKey is defined in RFC7517 and RFC7518.
RFC7518 Section 6.1 "kty" (Key Type) Parameter Values
"kty" Param Value | Key Type | Implementation Requirements |
---|---|---|
EC | Elliptic Curve [DSS] | Recommended+ |
RSA | RSA [RFC3447] | Required |
oct | Octet sequence (used to represent symmetric keys) | Required |
Thank you.