From 85fb8054bf000df52f1ca7388672d9e791bf05a7 Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Tue, 22 Apr 2025 10:31:18 -0400 Subject: [PATCH] Revert "update JWT realm docs to include at+jwt support (#1124)" This reverts commit 460e6d740679eb87627dfecd7ae1086e9f441d19. --- .../users-roles/cluster-or-deployment-auth/jwt.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md b/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md index d05003c40e..3e971621b9 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md @@ -218,14 +218,8 @@ The header claims indicate the token type and the algorithm used to sign the tok : (Required, String) Indicates the algorithm that was used to sign the token, such as `HS256`. The algorithm must be in the realm’s allow list. `typ` -: (Optional, String) Indicates the token type. - - For an ID token, this must be - - `JWT` - - For access tokens, this must be one of - - `JWT` - - `at+jwt` {applies_to}`stack: ga 9.1` +: (Optional, String) Indicates the token type, which must be `JWT`. + ### Payload claims [jwt-validation-payload]