rusackas commented on issue #27293:
URL: https://github.com/apache/superset/issues/27293#issuecomment-3940222117
Thanks for reporting this issue and to everyone who provided additional
context.
## Current Status
This issue has been identified as a **configuration requirement** that may
not be clearly documented.
## Workaround
As discovered by @drparavozik, the JWT token for async queries via WebSocket
requires the `GLOBAL_ASYNC_QUERIES` feature flag to be enabled:
1. In your `superset_config.py`, add or update:
```python
FEATURE_FLAGS = {
"GLOBAL_ASYNC_QUERIES": True,
}
```
2. Configure the other async query settings as documented:
```python
GLOBAL_ASYNC_QUERIES_JWT_SECRET = "your-32-byte-secret"
GLOBAL_ASYNC_QUERIES_TRANSPORT = "ws"
GLOBAL_ASYNC_QUERIES_REDIS_CONFIG = {
"port": REDIS_PORT,
"host": REDIS_HOST,
# ... other settings
}
```
3. Ensure `superset-websocket/config.json` uses the same `jwtSecret`
**Without the feature flag enabled, the JWT cookie will not be set at all**,
causing the "JWT not present" error.
## Related Work
PR #37809 is adding validation to fail fast with a clear error message when
async queries are misconfigured, which should prevent this silent failure mode
in the future.
## Request for Validation
Can those who reported this issue (@Haoran-Qi @amitdixit @ptdtan
@FullStackHan @thomasrea0113) confirm whether enabling the
`GLOBAL_ASYNC_QUERIES` feature flag resolves the issue?
If confirmed, we should update the async query documentation to clarify this
requirement.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
