From 5e19594ea488ace95dd42545a0077b7f8f243011 Mon Sep 17 00:00:00 2001 From: steve-chavez Date: Mon, 22 May 2023 16:28:04 -0300 Subject: [PATCH] auth: explain why jwt is used --- docs/references/auth.rst | 2 +- postgrest.dict | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/references/auth.rst b/docs/references/auth.rst index 9a53fd912..a25b08be1 100644 --- a/docs/references/auth.rst +++ b/docs/references/auth.rst @@ -42,7 +42,7 @@ This role switching mechanism is called **user impersonation**. In PostgreSQL it JWT-Based User Impersonation ---------------------------- -We use `JSON Web Tokens `_ to authenticate API requests. As you'll recall a JWT contains a list of cryptographically signed claims. All claims are allowed but PostgREST cares specifically about a claim called role. +We use `JSON Web Tokens `_ to authenticate API requests, this allows us to be stateless and not require database lookups for verification. As you'll recall a JWT contains a list of cryptographically signed claims. All claims are allowed but PostgREST cares specifically about a claim called role. .. code:: json diff --git a/postgrest.dict b/postgrest.dict index 92a3b4b87..9f01bfde9 100644 --- a/postgrest.dict +++ b/postgrest.dict @@ -83,6 +83,7 @@ Kofi Kubernetes localhost login +lookups Logins logins lon