From 791dd30cd0195335744169fa849cacc08cfa0853 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Tue, 16 Feb 2021 13:12:17 -0500 Subject: [PATCH] Update developing-with-nats/tutorials/jwt.md Co-authored-by: Colin Sullivan --- developing-with-nats/tutorials/jwt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/tutorials/jwt.md b/developing-with-nats/tutorials/jwt.md index d5faf32..2077714 100644 --- a/developing-with-nats/tutorials/jwt.md +++ b/developing-with-nats/tutorials/jwt.md @@ -327,7 +327,7 @@ A `nats-server` is configured to trust an operator. Meaning, the Operator JWT is part of its server configuration and requires a restart or `nats-server --signal reload` once changed. It is also configured with a way to obtain account JWT in one of 3 ways (explained below). Clients provide a user JWT on connect. Again the server or Account JWT is not configured with them. -They also posses the private NKEY corresponding the the JWT identity so they can proof their identity as described [above](#what-are-nkeys). +They also possess the private NKEY corresponding the the JWT identity so they can proof their identity as described [above](#what-are-nkeys). Through NKEY signature verification involved JWT are validated and the hierarchy between them can be verified.