From: Remi Tricot-Le Breton <rlebreton@haproxy.com>
Date: Thu, 10 Aug 2023 14:11:27 +0000 (+0200)
Subject: DOC: jwt: Add explicit list of supported algorithms
X-Git-Tag: v2.9-dev4~53
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=672203c26b5de129190a358265d6309eaff178b2;p=thirdparty%2Fhaproxy.git

DOC: jwt: Add explicit list of supported algorithms

Add explicit list of algorithms supported by the jwt_verify converter.
---

diff --git a/doc/configuration.txt b/doc/configuration.txt
index bb47a3f98b..b7f6f65373 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -18306,7 +18306,8 @@ jwt_verify(<alg>,<key>)
 
   For now, only JWS tokens using the Compact Serialization format can be
   processed (three dot-separated base64-url encoded strings). All the
-  algorithms mentioned in section 3.1 of RFC7518 are managed.
+  algorithms mentioned in section 3.1 of RFC7518 are managed (HS, ES, RS and PS
+  with the 256, 384 or 512 key sizes, as well as the special "none" case).
 
   If the used algorithm is of the HMAC family, <key> should be the secret used
   in the HMAC signature calculation. Otherwise, <key> should be the path to the