Added support for ES256 (ECDSA with P-256 and SHA-256) JWT signing algorithm.#34
Open
tomaskukol wants to merge 1 commit intonoha:masterfrom
Open
Added support for ES256 (ECDSA with P-256 and SHA-256) JWT signing algorithm.#34tomaskukol wants to merge 1 commit intonoha:masterfrom
tomaskukol wants to merge 1 commit intonoha:masterfrom
Conversation
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
1 participant
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.
This is a minimal implementation of ES256 JWT signing algorithm.
JWT ES256 (ECDSA using P-256 and SHA-256) is a secure, asymmetric signing algorithm used in OAuth 2.0, OpenID Connect, and API authentication to verify token integrity. It is commonly used in scenarios requiring high security with smaller signatures, such as in Apple services, mobile apps, IoT, modern web apps and banks.
You can see more details at spec (https://datatracker.ietf.org/doc/html/rfc7518#section-3.4).