sreejithac43 opened a new issue, #31492:
URL: https://github.com/apache/superset/issues/31492
### Bug description
I am getting an error:
"This session has encountered an interruption, and some controls may not
work as intended. If you are the developer of this app, please check that the
guest token is being generated correctly."
when using RLS filter in GuestToken for embedded dashboard when
"GLOBAL_ASYNC_QUERIES" = True. The same GuestToken set up works when
GLOBAL_ASYNC_QUERIES is not used
the errors I am getting in the dashboard network are "not authorised" for
charts and filter apis and the above quoted message on the top
Note:
I have celery worker and cache set up with a Redis server in both cases
token payload :
{
"user": {
"username": "guest",
"first_name": "guest",
"last_name": "guest"
},
"resources": [
{
"type": "dashboard",
"id": "d035c4d2-3e2c-4e3f-b45e-20ebb8b366e8"
}
],
"rls_rules": [
{
"clause": ""STATEID" = 3"
}
],
"iat": 1734112254.027939,
"exp": 1734112554.027939,
"aud": "http://0.0.0.0:8080/";,
"type": "guest"
}
I have seen discussion and PR in
https://github.com/apache/superset/pull/18924
https://github.com/apache/superset/issues/24171
and some in slack also addressing this bug but it says it was solved from
superset 3.1 and I am using latest superset in my docker pull
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.10
### Node version
I don't know
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [X] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [ ] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
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]
