From b0e12801a0b3c38efbd8c77e5f4aef20d76fbb48 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Tue, 16 Feb 2021 13:14:44 -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 9e2e46d..e7ff15d 100644 --- a/developing-with-nats/tutorials/jwt.md +++ b/developing-with-nats/tutorials/jwt.md @@ -577,7 +577,7 @@ JWT feature accounts pretty heavily, thus a few thing need to be clarified. It is possible to start out with less granular accounts and as applications grow in importance or scale become more fine grain. * Compared to file based config, Imports and Exports change slightly. To control who gets to import an export, activation tokens are introduced. - These are JWT that an importer can embed. + These are JWTs that an importer can embed. They comply to similar verification rules as user JWT, thus enabling a `nats-server` to check if the exporting account gave explicit consent. Due to the use of a token the exporting account's JWT does not have to be modified. * Updates of JWTs are applied as `nats-server` discover them.