Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ArgumentError (given 0, expected 1) with jwt 2.3.0 #9

Open
januszm opened this issue Jan 21, 2022 · 1 comment · May be fixed by #11
Open

ArgumentError (given 0, expected 1) with jwt 2.3.0 #9

januszm opened this issue Jan 21, 2022 · 1 comment · May be fixed by #11

Comments

@januszm
Copy link

januszm commented Jan 21, 2022

When loading the application code with keystores 0.4.0 and gem jwt in version 2.3.0 the following happens:

ArgumentError: wrong number of arguments (given 0, expected 1)
ruby/3.0.0/gems/keystores-0.4.0/lib/keystores/jks/pkcs8_key.rb:63:in `block in <class:RSA>'
ruby/3.0.0/gems/jwt-2.3.0/lib/jwt/jwk/rsa.rb:85:in `new'
...

It works fine with jwt 2.2.2 so a temporary solution is to lock the jwt version to lower than 2.3.0
@rylarson
Copy link
Owner

I probably need to release a major version change that gets rid of the hack to replace the new method on the OpenSSL classes. It was originally done to try to preserve OpenSSL API compatibility but it seems to have some unintended consequences.

@Quantenradierer Quantenradierer linked a pull request Jun 3, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: #9 adapt initialiser parameter to OpenSSL::PKey implementation Quantenradierer/keystores
2 participants
@januszm @rylarson