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:10:03 -05:00 committed by GitHub
parent 5b59c48216
commit 7df59d9af7
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

@ -359,7 +359,7 @@ Then safe yourself the complexity and do not use JWT. Regular config - possibly
##### JWT and Chain of Trust Verification ##### JWT and Chain of Trust Verification
Each JWT document has a subject it represents. This is the public identity NKEY represented by the JWT document. Each JWT document has a subject it represents. This is the public identity NKEY represented by the JWT document.
JWT documents contain an issueAt time when it was signed. JWT documents contain an `issueAt` time when it was signed.
This time is in seconds since Unix epoch. It is also used to determine which two JWT for the same subject is more recent. This time is in seconds since Unix epoch. It is also used to determine which two JWT for the same subject is more recent.
Furthermore JWT documents have an issuer, this may be an (identity) NKEY or a dedicated signing NKEY above it in the trust hierarchy. Furthermore JWT documents have an issuer, this may be an (identity) NKEY or a dedicated signing NKEY above it in the trust hierarchy.
A key is a signing key if it is listed as such in the JWT (above). A key is a signing key if it is listed as such in the JWT (above).