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:15:34 -05:00 committed by GitHub
parent 7b58a3cfe2
commit f4d43cdfdd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -574,7 +574,7 @@ A deeper understanding of accounts will help you to best setup NATS JWT based se
Our official suggestion is to scope accounts by application/service offered.
This is very fine grain and will require some configuration.
This is why some users gravitate to accounts per team. One account for all Applications of a team.
It is possible to start out with less granular accounts and as applications grow in importance or scale become more fine grain.
It is possible to start out with less granular accounts and as applications grow in importance or scale become more fine grained.
* Compared to file based config, Imports and Exports change slightly.
To control who gets to import an export, activation tokens are introduced.
These are JWTs that an importer can embed.