From 6554d3ff63623a329b0d93f7143d95cd3f19b3e6 Mon Sep 17 00:00:00 2001 From: JM Faircloth Date: Thu, 6 Jun 2024 15:03:59 -0500 Subject: [PATCH] remove upgrade guide to be added in separate PR --- .../content/docs/upgrading/upgrade-to-1.16.x.mdx | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/website/content/docs/upgrading/upgrade-to-1.16.x.mdx b/website/content/docs/upgrading/upgrade-to-1.16.x.mdx index c3aa75563bb0..7a5d52d2d1fb 100644 --- a/website/content/docs/upgrading/upgrade-to-1.16.x.mdx +++ b/website/content/docs/upgrading/upgrade-to-1.16.x.mdx @@ -81,19 +81,6 @@ userattr="userprincipalname" Refer to the [LDAP auth method (API)](/vault/api-docs/auth/ldap) page for more details on the configuration. -### JWT auth login requires bound audiences on the role - -JWT auth roles of type "jwt" require the `bound_audiences` claim to match at -least one of the JWT's `aud` claims. Prior to 1.16.3, the JWT auth method would -ignore token `aud` claims that were not a list of strings. - -The consequence of not configuring this correctly means users may not be able -to login to Vault. To fix the issue, update the role's `bound_audiences` -parameter to match the `aud` claim on the JWT. - -Refer to the [JWT auth method (API)](/vault/api-docs/auth/jwt) page for -more details on the configuration. - ## Known issues and workarounds @include 'known-issues/1_16-jwt_auth_config.mdx'