jimmy/postgrest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify config and auth sections on JWKS.

Browse Source 
See PostgREST/postgrest#1205.
This commit is contained in:
Russell Davies
2018-11-15 11:11:24 -05:00
committed by Steve Chávez
parent 9475f53fd7
commit 6d1adaaa54
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
install.rst
+1 -1
View File
@@ -167,7 +167,7 @@ server-proxy-uri
jwt-secret
----------
The secret or `JSON Web Key (JWK) <https://tools.ietf.org/html/rfc7517>`_ used to decode JWT tokens clients provide for authentication. For security the key must be **at least 32 characters long**. If this parameter is not specified then PostgREST refuses authentication requests. Choosing a value for this parameter beginning with the at sign such as :code:`@filename` loads the secret out of an external file. This is useful for automating deployments. Note that any binary secrets must be base64 encoded. Both symmetric and asymmetric cryptography are supported. For more info see :ref:`asym_keys`.
The secret or `JSON Web Key (JWK) (or set) <https://tools.ietf.org/html/rfc7517>`_ used to decode JWT tokens clients provide for authentication. For security the key must be **at least 32 characters long**. If this parameter is not specified then PostgREST refuses authentication requests. Choosing a value for this parameter beginning with the at sign such as :code:`@filename` loads the secret out of an external file. This is useful for automating deployments. Note that any binary secrets must be base64 encoded. Both symmetric and asymmetric cryptography are supported. For more info see :ref:`asym_keys`.
.. _jwt-aud: