From 7df59d9af77d3718ffb5fd234038ad4f1a114138 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Tue, 16 Feb 2021 13:10:03 -0500 Subject: [PATCH] Update developing-with-nats/tutorials/jwt.md Co-authored-by: Colin Sullivan --- developing-with-nats/tutorials/jwt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/tutorials/jwt.md b/developing-with-nats/tutorials/jwt.md index 8e0a238..9e221a3 100644 --- a/developing-with-nats/tutorials/jwt.md +++ b/developing-with-nats/tutorials/jwt.md @@ -359,7 +359,7 @@ Then safe yourself the complexity and do not use JWT. Regular config - possibly ##### 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. -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. 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).