[1.14.x] Doc fixes

docs/content/guides/security/auth/jwt/_index.md

@@ -45,7 +45,7 @@ Inside the JWT various *claims* are encoded; claims provide identity information
 - `aud`: The audience the token was issued for. This is an important security feature that makes sure that a token 
 issued for one use cannot be used for other purposes.
 
-See the [JWT specification](https://tools.ietf.org/html/rfc7519#section-4.1) for a complete description of all standard claims.
+See the [JWT specification](https://datatracker.ietf.org/doc/html/rfc7519#section-4.1) for a complete description of all standard claims.
 
 The claims are encoded as a JSON object, and then encoded with base64 to form the payload of the JWT
 

docs/content/guides/security/auth/jwt/access_control/_index.md

@@ -447,7 +447,7 @@ jq '.+{alg:"RS256"}|.+{use:"sig"}' jwks.json | tee tmp.json && mv tmp.json jwks.
 {{< /highlight >}}
 
 {{% notice note %}}
-For details about the above JWT fields, see <b>[this section](https://tools.ietf.org/html/rfc7517#section-4)</b> of the JWT specification. 
+For details about the above JWT fields, see <b>[this section](https://datatracker.ietf.org/doc/html/rfc7517#section-4)</b> of the JWT specification. 
 {{% /notice %}}
 
 Finally, let's turn the single key into a key set: