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

View File

@ -582,7 +582,7 @@ JWT feature accounts pretty heavily, thus a few thing need to be clarified.
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.
* How this is done depends on the resolver.
* `mem-resolver` require `nats-server --signal reload` to re-read all configured account JWT.
* `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.
* `nats-resolver` will also also update the corresponding JWT file and compensate in case the update message was not received due to temporary disconnect.
* User JWTs do only depend on the issuing Account NKEY only, they do NOT depend on a particular version of an Account JWT.