Skip to content

chore: bump PyJWT to 2.9 for PyJWKClient JWKS caching - #387

Open
yakusevv wants to merge 2 commits into
openimis:release/26.10from
yakusevv:chore/bump-pyjwt-2-9
Open

yakusevv wants to merge 2 commits into
openimis:release/26.10from
yakusevv:chore/bump-pyjwt-2-9

Conversation

@yakusevv

Copy link
Copy Markdown
Contributor

PyJWT~=2.4.0 → PyJWT~=2.9.0.

PyJWKClient gained the arguments needed to cache a JWKS — cache_keys, lifespan — plus timeout in 2.6. On 2.4 there is no way to cache signing keys, so any OIDC token validation has to fetch the provider's JWKS on the request path. This unblocks that work; nothing in the current code changes behaviour.

Compatibility

  • Across the 53 installed modules, only core/jwt.py and core/jwt_authentication.py import jwt directly, so the surface is small.
  • django-graphql-jwt==0.3.4 requires PyJWT>=2,<3 — 2.9 satisfies it.

Verification, on 2.9

  • manage.py test core — 204 tests, OK
  • manage.py test opensearch_reports — 10 tests, OK (covers the JWT-cookie authentication path)

@zikani03
zikani03 changed the base branch from develop to release/26.10 September 16, 2026 12:06
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

Successfully merging this pull request may close these issues.

2 participants