From: zadevhub <138465437+zadevhub@users.noreply.github.com> Date: Sun, 24 May 2026 10:29:22 +0000 (+0100) Subject: 📝 Update `docs/en/docs/tutorial/security/oauth2-jwt.md` (#14781) X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=21c46919fc14f6541397ff5bdc77d9c806e7b33e;p=thirdparty%2Ffastapi%2Ffastapi.git 📝 Update `docs/en/docs/tutorial/security/oauth2-jwt.md` (#14781) Co-authored-by: Sebastián Ramírez Co-authored-by: Yurii Motov <109919500+YuriiMotov@users.noreply.github.com> --- diff --git a/docs/en/docs/tutorial/security/oauth2-jwt.md b/docs/en/docs/tutorial/security/oauth2-jwt.md index 983da9a85..6c1ab27b2 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.