Skip to content

feat: utilize nats-io jwt claims validation prior to signing#166

Merged
choufraise merged 2 commits intomainfrom
feat/jwt-validation
Mar 18, 2026
Merged

feat: utilize nats-io jwt claims validation prior to signing#166
choufraise merged 2 commits intomainfrom
feat/jwt-validation

Conversation

@choufraise
Copy link
Collaborator

Instead of doing our own minimalistic claims validation we should rely on the existing validation mechanism provided by the nats-io jwt lib.

Bump nats-io/jwt/v2 to v2.8.1 ensure multi-import of same service from different accounts (applicable in e.g. JetStream Flow Control case ($JS.FC.>). Verify using local test.

Closes: #165

Signed-off-by: Thobias Karlsson <thobias.karlsson@gmail.com>
Instead of doing our own minimalistic claims validation we should rely on the existing validation mechanism provided by the nats-io jwt lib.

Bump nats-io/jwt/v2 to v2.8.1 ensure multi-import of same service from different accounts (applicable in e.g. JetStream Flow Control case (`$JS.FC.>`). Verify using local test.

Closes: #165
Signed-off-by: Thobias Karlsson <thobias.karlsson@gmail.com>
@choufraise choufraise requested a review from a team as a code owner March 18, 2026 07:11
Copy link
Collaborator

@eufriction eufriction left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@choufraise choufraise merged commit 63a2b13 into main Mar 18, 2026
6 checks passed
@choufraise choufraise deleted the feat/jwt-validation branch March 18, 2026 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

nauth should validate jwt using nats-io validation before encoding

3 participants