Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / jwt/ruby-jwt issues and pull requests

#519 - fix: GitHub workflow files indentation

Pull Request - State: closed - Opened by MatteoPierro almost 2 years ago

#518 - JWK Parameters

Issue - State: closed - Opened by bellebaum almost 2 years ago - 6 comments

#517 - Smoke test for built gem

Issue - State: closed - Opened by anakinj almost 2 years ago
Labels: feature, up for grabs

#516 - Exclude files not relevant for release

Pull Request - State: closed - Opened by anakinj almost 2 years ago

#515 - Include gemfile in action name

Pull Request - State: closed - Opened by anakinj almost 2 years ago

#514 - set rubygems_mfa_required to true for gemspec

Pull Request - State: closed - Opened by anakinj almost 2 years ago

#513 - Update to RuboCop 1.31.0

Pull Request - State: closed - Opened by anakinj almost 2 years ago

#512 - Support algorithm to be given as a class

Pull Request - State: closed - Opened by anakinj about 2 years ago - 1 comment

#511 - main branch references

Pull Request - State: closed - Opened by anakinj about 2 years ago

#510 - Allow algorithm to be a class

Pull Request - State: closed - Opened by anakinj about 2 years ago - 1 comment

#509 - Memory problems in JWT.decode

Issue - State: closed - Opened by jamesarosen about 2 years ago - 9 comments

#508 - SourceLevel is not relevant anymore

Pull Request - State: closed - Opened by anakinj about 2 years ago

#507 - Next iteration

Pull Request - State: closed - Opened by anakinj about 2 years ago

#506 - Release v2.5.0

Pull Request - State: closed - Opened by anakinj about 2 years ago - 1 comment

#505 - Is there a way to ignore payload key ordering?

Issue - State: closed - Opened by ekampp about 2 years ago - 2 comments

#504 - Explicit loading of jwt/version to make it available for a built gem

Pull Request - State: closed - Opened by anakinj about 2 years ago

#503 - Question: how to use Google API's JWKS uri when encoding JWT payload

Issue - State: closed - Opened by mchavarriagam about 2 years ago - 2 comments

#502 - Fix NoMethodError when a 2 segment token is missing 'alg' header

Pull Request - State: closed - Opened by cmrd-senya about 2 years ago - 5 comments

#499 - Potential JWK KeyFinder Denial of Service

Issue - State: closed - Opened by liamdawson about 2 years ago - 5 comments

#496 - Support OpenSSL >= 3.0

Pull Request - State: closed - Opened by anakinj over 2 years ago - 3 comments

#495 - Use OpenSSL 3

Issue - State: closed - Opened by guillaumewrobel over 2 years ago - 15 comments

#494 - Improved RSA signing and verification

Pull Request - State: closed - Opened by anakinj over 2 years ago - 2 comments

#487 - JWT.decode broken in v2.4: `unpack1': invalid base64 (ArgumentError)

Issue - State: closed - Opened by collimarco over 2 years ago - 11 comments

#478 - On Keys and Algorithms

Issue - State: open - Opened by bellebaum over 2 years ago - 5 comments
Labels: documentation, discussion, security

#474 - Use RFC 7638 JWK Thumbprints as kid

Issue - State: closed - Opened by bellebaum over 2 years ago - 4 comments

#473 - Support JWK public URL

Issue - State: closed - Opened by santhanakarthikeyan over 2 years ago - 2 comments

#460 - Ability to extend JWT encoding and decoding behaviour

Pull Request - State: closed - Opened by anakinj almost 3 years ago - 4 comments

#455 - RBS signatures

Issue - State: open - Opened by HoneyryderChuck almost 3 years ago - 7 comments

#439 - Raise a JWT::DecodeError when token is not a String

Pull Request - State: closed - Opened by kalilz4485 about 3 years ago - 4 comments

#435 - ArgumentError in `verify': wrong number of arguments (given 3, expected 1)

Issue - State: closed - Opened by yazinsai about 3 years ago - 5 comments

#412 - OpenSSL::PKey::EC::Point::Error: EC_POINT_bn2point: invalid encoding when importing a JWK

Issue - State: closed - Opened by fabn over 3 years ago - 22 comments
Labels: review required, possible bug

#400 - Resolving algorithms from JWK when not explicitly specified

Issue - State: open - Opened by MatteoPierro almost 4 years ago - 1 comment
Labels: discussion

#398 - Improved public interfaces for JWK classes by splitting them by capabilities

Pull Request - State: closed - Opened by anakinj almost 4 years ago - 2 comments

#394 - Support for OKP JWK keys

Issue - State: closed - Opened by anakinj almost 4 years ago - 2 comments
Labels: feature

#393 - Fix Time.now casting causing false positive in verify_at

Pull Request - State: open - Opened by kevinreedy almost 4 years ago - 2 comments

#389 - How to use a 'signing key' as used by next-auth

Issue - State: closed - Opened by recurser almost 4 years ago - 3 comments

#364 - Example unsigned token that bypasses verification

Issue - State: closed - Opened by brianlow about 4 years ago - 11 comments

#362 - failing on secp256r1 curve

Issue - State: closed - Opened by m-zielinski about 4 years ago - 7 comments
Labels: security, possible bug

#353 - Issued At RFC type mismatch causing false postives on verify_at

Issue - State: open - Opened by ghost over 4 years ago - 10 comments
Labels: enhancement, bug

#352 - Improve support for Unsecured JWT

Pull Request - State: open - Opened by hesalx over 4 years ago - 3 comments
Labels: enhancement

#350 - JWT::ExpiredSignature raised for non-JSON payloads

Issue - State: closed - Opened by volmer over 4 years ago - 6 comments

#340 - What is secret when using RSA keypair

Issue - State: closed - Opened by schowdhury almost 5 years ago - 5 comments
Labels: documentation, discussion

#334 - Wrong `alg` used in header for Ed25519 keys

Issue - State: open - Opened by zblach about 5 years ago - 14 comments
Labels: discussion

#323 - When using none alg (no signature), should the claims verification be ignored?

Issue - State: open - Opened by glasses618 over 5 years ago - 4 comments
Labels: review required, possible bug

#322 - HS512256 OpenSSL Exception: First num too large

Issue - State: closed - Opened by RootTJNII over 5 years ago - 6 comments

#309 - Support for Unencoded Payload Option (RFC 7797)

Issue - State: open - Opened by idigber over 5 years ago - 6 comments
Labels: enhancement, documentation, feature, up for grabs

#307 - Set default issued at time

Issue - State: closed - Opened by derosm2 over 5 years ago - 2 comments
Labels: discussion

#305 - Make JWT::Signature.verify return true on success

Pull Request - State: closed - Opened by bdewater over 5 years ago - 5 comments
Labels: enhancement

#304 - Could you add fixtures for PS-algorithms in specs?

Issue - State: closed - Opened by lolgear over 5 years ago - 2 comments
Labels: enhancement

#270 - Claim and signature validations without raising exceptions

Issue - State: open - Opened by jec over 6 years ago - 1 comment
Labels: enhancement, documentation, feature, discussion, refactoring

#249 - JWT.encode method breaking changes

Issue - State: closed - Opened by msxavi almost 7 years ago - 7 comments
Labels: discussion

#246 - JSON support

Issue - State: closed - Opened by msroot almost 7 years ago - 3 comments
Labels: enhancement, feature, review required, help wanted, up for grabs

#244 - Ensure presence of claims

Issue - State: closed - Opened by curlyfingers almost 7 years ago - 8 comments
Labels: enhancement, documentation, discussion, up for grabs

#208 - Documentation for using a key finder with JWT.decode

Issue - State: open - Opened by matt-murdock over 7 years ago - 4 comments
Labels: documentation

#170 - verify_iss: true is raising JWT::DecodeError instead of JWT::InvalidIssuerError

Issue - State: closed - Opened by scalp42 about 8 years ago - 5 comments

#158 - Support for JWK in-lieu of rsa_public

Issue - State: closed - Opened by caldwecr about 8 years ago - 8 comments
Labels: enhancement, feature, discussion, security, help wanted, up for grabs

#124 - Verify tokens without throwing exceptions

Issue - State: open - Opened by kwando over 8 years ago - 10 comments
Labels: feature, discussion

#110 - Suggest passing block to JWT.decode for claim verification

Issue - State: open - Opened by kjwierenga almost 9 years ago - 7 comments
Labels: enhancement, discussion, help wanted, up for grabs

#103 - make sure :sub check behaves like :aud check

Pull Request - State: closed - Opened by skippy about 9 years ago - 1 comment

#102 - aud verifies if aud is passed in, :sub does not

Issue - State: closed - Opened by skippy about 9 years ago - 1 comment
Labels: bug

#101 - Change hash syntax

Pull Request - State: closed - Opened by excpt about 9 years ago - 1 comment

#95 - Options hash uses both symbols and strings as keys.

Issue - State: closed - Opened by aj-michael about 9 years ago - 6 comments
Labels: discussion

#81 - Shouldn't verification of additional claims, like iss, aud etc. be enforced when in options?

Issue - State: closed - Opened by lwe over 9 years ago - 8 comments
Labels: bug

#80 - Introduce JWE support

Issue - State: open - Opened by soumyaray over 9 years ago - 11 comments
Labels: enhancement, feature, help wanted, up for grabs

#59 - Support verifying signature signed using x5c header

Issue - State: closed - Opened by punkle over 9 years ago - 10 comments
Labels: enhancement, feature, up for grabs

#50 - Preperations for version 2.x

Issue - State: closed - Opened by excpt over 9 years ago

#49 - Preperations for version 2.x

Pull Request - State: closed - Opened by excpt over 9 years ago