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.

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

Incompatibility Issue: pyjwt==2.8.0 with cryptography==43.0.0 causes jwt.exceptions.PyJWKSetError #966

Open
CherryNick opened this issue Jul 24, 2024 · 3 comments

Comments

@CherryNick
Copy link

CherryNick commented Jul 24, 2024

Summary
When using pyjwt==2.8.0 with cryptography==43.0.0, an error occurs:

jwt.exceptions.PyJWKSetError: The JWK Set did not contain any usable keys. Perhaps 'cryptography' is not installed?

Downgrading cryptography to 42.0.7 resolves the issue, indicating an incompatibility between these specific versions.

Expected Result
The JWT token should decode successfully without errors when using pyjwt==2.8.0 and cryptography==43.0.0.

Actual Result
An error is raised when attempting to decode a JWT token:

jwt.exceptions.PyJWKSetError: The JWK Set did not contain any usable keys. Perhaps 'cryptography' is not installed?

Reproduction Steps

  • Install pyjwt==2.8.0 and cryptography==43.0.0.
  • Attempt to decode a JWT token using a JWK set.
  • Observe the error: jwt.exceptions.PyJWKSetError.

Workaround
Downgrading cryptography to version 42.0.7 resolves the issue

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Issues without activity for more than 60 days label Sep 23, 2024
@toddgardner
Copy link

cryptography<43.0.1 is pinning a vulnerable version of pyopenssl (effected by https://openssl-library.org/news/secadv/20240903.txt) so PyJWT's dependancies probably need to handle the new version.

@github-actions github-actions bot removed the stale Issues without activity for more than 60 days label Sep 26, 2024
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Issues without activity for more than 60 days label Nov 25, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 2, 2024
@auvipy auvipy removed the stale Issues without activity for more than 60 days label Feb 5, 2025
@auvipy auvipy reopened this Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants