Add Ed25519 key support#16
Open
manojpr-cb wants to merge 4 commits into
Open
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
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.
What
Adds Ed25519 (EdDSA) signing support to the JWT auth path, alongside the existing ECDSA (ES256) keys.
generateJwtnow detects the key type and signs accordingly:JWSSigner, so no new dependency is needed (nimbus would otherwise require Tink for OKP keys). EC keys are normalized through the default provider so the existing ECDSA path is unchanged.SDK_VERSIONso the User-Agent reports the right version.Testing
Verified against the live API with both ECDSA and Ed25519 keys: JWT structural checks (alg, kid, sub, nbf/exp, distinct nonces, signature verifies), a malformed-secret negative case, plus real REST calls all pass.