Backport of OIDC: add note on PKCE support for code flow into release…

…/1.9.x (#13862) * backport of commit 64940e3 * backport of commit f96424f * backport of commit 729e11a Co-authored-by: JM Faircloth <[email protected]>
hashicorp · Feb 1, 2022 · 21696d1 · 21696d1
1 parent 812037d
commit 21696d1
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/website/content/docs/auth/jwt/index.mdx b/website/content/docs/auth/jwt/index.mdx
@@ -28,7 +28,8 @@ examples of OIDC and JWT usage.
 This section covers the setup and use of OIDC roles. If a JWT is to be provided directly,
 refer to the [JWT Authentication](/docs/auth/jwt#jwt-authentication) section below. Basic
 familiarity with [OIDC concepts](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1)
-is assumed.
+is assumed. The Authorization Code flow makes use of the Proof Key for Code
+Exchange (PKCE) extension.
 
 Vault includes two built-in OIDC login flows: the Vault UI, and the CLI
 using a `vault login`.