Closed christophehenry closed 1 year ago
We've seen this issue as well, somewhere between 2.4.0 and 2.6.0.
I think this issue was already inside 2.5.0. I did some digging, and there's already a comment with an explanation: https://github.com/jpadilla/pyjwt/issues/806#issuecomment-1252200704
From this, I think it's safe to just update the tests with new JWTs or change your tests to only test validity :)
Nice find @jensjeflensje! Thanks!
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
A project I work on updated from 2.4.0 to 2.6.0 today and, suddenly, our tests stopped passing. It turns out that some of our tests are checking against the generated JWT and the signature part has changed between 2.4.0 and 2.6.0.
Expected Result
The generated JWT should be consistant between versions.
Actual Result
The signature part of the generated JWT changed between 2.4.0 and 2.6.0 without any other configuration change
Reproduction Steps
System Information