Docs: JWT Troubleshooting Doc Updation (#18602)

This commit is contained in:
RounakDhillon 2024-11-12 15:47:23 +05:30 committed by GitHub
parent 8526687506
commit ea56a86c48
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 12 additions and 0 deletions

View File

@ -45,3 +45,9 @@ You can validate that in [jwt.io](https://jwt.io/). if there's something wrong o
alt="jwt.io" alt="jwt.io"
caption="jwt.io tool for validating JWT claims" 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`.

View File

@ -45,3 +45,9 @@ You can validate that in [jwt.io](https://jwt.io/). if there's something wrong o
alt="jwt.io" alt="jwt.io"
caption="jwt.io tool for validating JWT claims" 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`.