From ea56a86c48a677809dc2360c1e7b283ca40a64d2 Mon Sep 17 00:00:00 2001 From: RounakDhillon <162090200+RounakDhillon@users.noreply.github.com> Date: Tue, 12 Nov 2024 15:47:23 +0530 Subject: [PATCH] Docs: JWT Troubleshooting Doc Updation (#18602) --- .../v1.5.x/deployment/security/jwt-troubleshooting.md | 6 ++++++ .../deployment/security/jwt-troubleshooting.md | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/openmetadata-docs/content/v1.5.x/deployment/security/jwt-troubleshooting.md b/openmetadata-docs/content/v1.5.x/deployment/security/jwt-troubleshooting.md index b6c1e8299b9..e3c8158d7f0 100644 --- a/openmetadata-docs/content/v1.5.x/deployment/security/jwt-troubleshooting.md +++ b/openmetadata-docs/content/v1.5.x/deployment/security/jwt-troubleshooting.md @@ -45,3 +45,9 @@ You can validate that in [jwt.io](https://jwt.io/). if there's something wrong o alt="jwt.io" caption="jwt.io tool for validating JWT claims" /%} + +### Resolving the "Failed in filtering request: Not Authorized! Token not present" Error + +If you encounter the error message **"Failed in filtering request: Not Authorized! Token not present"**, verify the **`enableSecureSocketConnection`** environment setting. + +Ensure that **`enableSecureSocketConnection: ${AUTHORIZER_ENABLE_SECURE_SOCKET:-false}`** is set to `false` if it is currently set to `true`. diff --git a/openmetadata-docs/content/v1.6.x-SNAPSHOT/deployment/security/jwt-troubleshooting.md b/openmetadata-docs/content/v1.6.x-SNAPSHOT/deployment/security/jwt-troubleshooting.md index b6c1e8299b9..e3c8158d7f0 100644 --- a/openmetadata-docs/content/v1.6.x-SNAPSHOT/deployment/security/jwt-troubleshooting.md +++ b/openmetadata-docs/content/v1.6.x-SNAPSHOT/deployment/security/jwt-troubleshooting.md @@ -45,3 +45,9 @@ You can validate that in [jwt.io](https://jwt.io/). if there's something wrong o alt="jwt.io" caption="jwt.io tool for validating JWT claims" /%} + +### Resolving the "Failed in filtering request: Not Authorized! Token not present" Error + +If you encounter the error message **"Failed in filtering request: Not Authorized! Token not present"**, verify the **`enableSecureSocketConnection`** environment setting. + +Ensure that **`enableSecureSocketConnection: ${AUTHORIZER_ENABLE_SECURE_SOCKET:-false}`** is set to `false` if it is currently set to `true`.