fix: use JWTPublicKey for ECDSA token parsing by lakhansamani · Pull Request #487 · authorizerdev/authorizer

Skip to content

Navigation Menu

Sign in

Appearance settings

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Conversation

@lakhansamani

Copy link Copy Markdown

Contributor

Summary

  • Fixed ECDSA (ES256/ES384/ES512) token parsing to use JWTPublicKey instead of JWTSecret
  • Signing correctly used JWTPrivateKey but parsing was incorrectly using JWTSecret

Test plan

  • Verify ECDSA token signing and parsing works correctly
  • Run existing JWT tests

Fixes #476

The ParseJWTToken function incorrectly used JWTSecret instead of
JWTPublicKey for ECDSA (ES256/ES384/ES512) token validation.

Fixes #476

@lakhansamani lakhansamani merged commit fca7aed into main

Mar 1, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

ECDSA JWT parsing uses JWTSecret instead of JWTPublicKey

1 participant

@lakhansamani