ruby-jwt
ruby-jwt copied to clipboard
jwt
A ruby implementation of the RFC 7519 OAuth JSON Web Token (JWT) standard.
See: [RFC 7516 4.1.3](https://datatracker.ietf.org/doc/html/rfc7516#section-4.1.3) I am working with: - [Smart Health Cards - Overview](https://smarthealth.cards/) - [Smart Health Cards - Specification](https://spec.smarthealth.cards/) in Ruby. I'm working in a constrained Ruby environment (Rhomobile...
I've noticed that `jwt` doesn't ship with rbs signatures yet. Is this something the project would like to have going forward?
Hello, Currently when doing ```ruby JWT.decode(nil, nil) ``` You get a `JWT::DecodeError (Nil JSON web token)` or ```ruby JWT.decode('invalid', nil) ``` You get a `JWT::DecodeError (Not enough or too many...
I'm using the sample code shown in the README for `RS256`: ```ruby rsa_private = OpenSSL::PKey::RSA.generate 2048 rsa_public = rsa_private.public_key token = JWT.encode payload, rsa_private, 'RS256' decoded_token = JWT.decode token, rsa_public,...
Minimal reproducible case: ```ruby key_hash = { crv: "P-521", kid: "6f1cb481-c032-4e46-8f62-fe68c634a125", kty: "EC", use: "sig", x: "AMNQr/q+YGv4GfkEjrXH2N0+hnGes4cCqahJlV39m3aJpqSK+uiAvkRE5SDm2bZBc3YHGzhDzfMTUpnvXwjugUQP", y: "fIwouWsnp44Fjh2gBmO8ZafnpXZwLOCoaT5itu/Q4Z6j3duRfqmDsqyxZueDA3Gaac2LkbWGplT7mg4j7vCuGsw=" } JWT::JWK.import(key_hash) ``` Getting this error (gem is current master, 2cea14fdae439773fafc59640178e5cf7a0af8a4)...
Hello there, We had some troubles with `ruby-jwt` in production recently. The reason was that we put the unix timestamp as seconds since epoch in `iat`, but inside `verify_iat` ruby-jwt...
on it currently says > Current version: 1.5.6 and the last changelog update was 2016-09-19
The example tokens in this library use `"alg": "ED25519"`, but the related spec seems to suggest that it be `"EdDSA"` instead. https://tools.ietf.org/html/rfc8037#appendix-A.4
Currently, `JWT.decode` always expects to have the algorithms provided by the client. When using JWKs this information can be redundant since supported algorithms can be resolved from the provided keys....
While working on the OKP support (#388) I realised that the public API for the JWK classes was too narrow. This probably because the initial implementation was based on the...
