fix: use curve-matching EC keys for ES384/ES512 backend tests#963
Merged
vgrozdanic merged 3 commits intomasterfrom Feb 11, 2026
Merged
fix: use curve-matching EC keys for ES384/ES512 backend tests#963vgrozdanic merged 3 commits intomasterfrom
vgrozdanic merged 3 commits intomasterfrom
Conversation
This reverts commit 6896191.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After merging a couple of PRs, CI has started failing because newer PyJWT versions enforce EC curve/algorithm compatibility and we were using ES256 in all tests.
I have generated keys locally, tried using well known JWKs but PyJWT < 2.0 doesn't support decoding JWK.
Changes: