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:36 -05:00 committed by GitHub
parent 78b1fdd722
commit 077dae642f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -580,7 +580,7 @@ JWT feature accounts pretty heavily, thus a few thing need to be clarified.
These are JWT 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 JWT are applied as `nats-server` discover them.
* Updates of JWTs are applied as `nats-server` discover them.
* How this is done depends on the resolver.
* `mem-resolver` require `nats-server --signal reload` to re-read all configured account JWTs.
* `url-resolver` and `nats-resolver` listen on a dedicated update subject of the system account and applied if the file is valid.