From 5a160715fa3269a5748e21a02860e48d6e0e32fc Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Mon, 15 Feb 2021 12:45:55 -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 3d4312d..7389fe1 100644 --- a/developing-with-nats/tutorials/jwt.md +++ b/developing-with-nats/tutorials/jwt.md @@ -302,7 +302,7 @@ Relying on a hierarchial chain of trust between three distinct NKEYs and associa 3. User: corresponds to one user's configuration Each NKEY is referenced, with additional configuration in a JWT document. -Each JWT has a subject and it's value is the public portion of an NKEY and serves as identity. +Each JWT has a subject field and its value is the public portion of an NKEY and serves as identity. Names exist in JWT but as of now are only used by tooling, `nats-server` does not read this value. The referenced NKEY's role determines the JWT content.