1
0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00

Update developing-with-nats/tutorials/jwt.md

Co-authored-by: Colin Sullivan <colin@synadia.com>
This commit is contained in:
Matthias Hanel 2021-02-16 13:14:44 -05:00 committed by GitHub
parent 077dae642f
commit b0e12801a0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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.