From 21c46919fc14f6541397ff5bdc77d9c806e7b33e Mon Sep 17 00:00:00 2001 From: zadevhub <138465437+zadevhub@users.noreply.github.com> Date: Sun, 24 May 2026 11:29:22 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Update=20`docs/en/docs/tutorial/?= =?UTF-8?q?security/oauth2-jwt.md`=20(#14781)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Sebastián Ramírez Co-authored-by: Yurii Motov <109919500+YuriiMotov@users.noreply.github.com> --- docs/en/docs/tutorial/security/oauth2-jwt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/docs/tutorial/security/oauth2-jwt.md b/docs/en/docs/tutorial/security/oauth2-jwt.md index 983da9a859..6c1ab27b27 100644 --- a/docs/en/docs/tutorial/security/oauth2-jwt.md +++ b/docs/en/docs/tutorial/security/oauth2-jwt.md @@ -18,7 +18,7 @@ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4 It is not encrypted, so, anyone could recover the information from the contents. -But it's signed. So, when you receive a token that you emitted, you can verify that you actually emitted it. +But it's signed. So, when you receive a token that you issued, you can verify that it was you who issued it. That way, you can create a token with an expiration of, let's say, 1 week. And then when the user comes back the next day with the token, you know that user is still logged in to your system.