natasha-tc opened a new issue, #35261:
URL: https://github.com/apache/superset/issues/35261

   ### Bug description
   
   Current Superset version: 4.0.2
   
   Our platform is set up to embed Superset charts, but we frequently encounter 
timeout errors in the platform when viewing Superset dashboards.
   
   What we have found is the Superset integration uses a library 
(@superset-ui/embedded-sdk) to display dashboards. This library creates 
temporary guest tokens each time a dashboard is viewed — even if the user 
hasn’t directly logged into Superset. After a timeout (e.g., 15 minutes), the 
library automatically tries to refresh these tokens. If the user has logged out 
or their session has ended, these refresh attempts fail, triggering 
"Insufficient Permissions" errors. The problem worsens if multiple dashboards 
are viewed, as more tokens are created and retried in parallel.
   
   Can you please get assistance on a proper resolution for this issue?
   
   <img width="679" height="597" alt="Image" 
src="https://github.com/user-attachments/assets/ee898b43-857e-4d02-90dc-f7eb564e4448";
 />
   
   ### Screenshots/recordings
   
   Attached is an example of the error message displayed upon being logged out 
while viewing charts
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   I don't know
   
   ### 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]

Reply via email to