Skip to content

Commit

Permalink
See open-metadata/OpenMetadata@ea56a86 from refs/heads/main
Browse files Browse the repository at this point in the history
  • Loading branch information
open-metadata committed Nov 12, 2024
1 parent 157dcd7 commit 01a9b58
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 0 deletions.
6 changes: 6 additions & 0 deletions content/v1.5.x/deployment/security/jwt-troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -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`.
Original file line number Diff line number Diff line change
Expand Up @@ -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`.

0 comments on commit 01a9b58

Please sign in to comment.