Browse Source

fix(docs) Added docs on how to define tokens (#2018)

* added docs on how to define tokens

* fixed typo

Co-authored-by: James Green <james.green@affinity-digtal.com>
release-8443
James Green 3 years ago
parent
commit
dd18b59dd3
No account linked to committer's email address
1 changed files with 1 additions and 0 deletions
  1. 1
    0
      doc/tokens.md

+ 1
- 0
doc/tokens.md View File

22
 - 'aud' application identifier. This value indicates what service is consuming the token.  It should be negotiated with the service provider before generating the token.
22
 - 'aud' application identifier. This value indicates what service is consuming the token.  It should be negotiated with the service provider before generating the token.
23
 
23
 
24
 The secret is used to compute the HMAC hash value and verify the token for HS256 tokens.  
24
 The secret is used to compute the HMAC hash value and verify the token for HS256 tokens.  
25
+- It is now possible to define the algorithm type used, simply update the prosody.cfg.lua file with your chosen type. e.g `signature_algorithm = "HS512"`
25
 
26
 
26
 Alternately the token may be signed by a private key and authorized via a public keyserver using RS256 tokens.  In this mode, the 'kid' header of the JWT must be set to the name of the public key.  The backend server must be configured to fetch and confirm keys from a pre-configured public keyserver.
27
 Alternately the token may be signed by a private key and authorized via a public keyserver using RS256 tokens.  In this mode, the 'kid' header of the JWT must be set to the name of the public key.  The backend server must be configured to fetch and confirm keys from a pre-configured public keyserver.
27
 
28
 

Loading…
Cancel
Save