taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

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

Browse Source 
Co-authored-by: Colin Sullivan <colin@synadia.com>
This commit is contained in:
Matthias Hanel 2021-02-16 13:16:39 -05:00 committed by GitHub
parent ec7f47d2d2
commit cd15efef82
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
developing-with-nats/tutorials/jwt.md
View File

@ -635,7 +635,7 @@ Thus, depending on your scenario, relevant identity NKEYS need to only exist in
The store directory contains JWT fora operator/account/user and does not contain key material.
Therefore it is ok to back these up or even store them in a VCS such as git.
But be aware that depending on content, JWT may reveal which permissions/subjects/public-nkeys exist.
Knowing the content of a JWT does not grant access, only holding the keys does.
Knowing the content of a JWT does not grant access; only private keys will.
However, organization may not wish to make those public outright and thus has to make sure that these external systems are secured appropriately.
When restoring an older version, be aware that: