furkanrollic opened a new issue, #32219:
URL: https://github.com/apache/superset/issues/32219

   ### Bug description
   
   After 5.0.0rc1 update dashboard embeddings do not work. First we got 
problems with **api/v1/security/guest_token** endpoint related to this issue 
https://github.com/apache/superset/issues/31675. We have managed to pass that 
by downgrading to PyJWT==2.9.0 in superset container but now we got this error.
   
   Guest token is created like this. When we embed dashboard it only displays 
filters and all the charts fails to display with the error in the title.
   ```
   {
     "user": {
       "username": "**",
       "first_name": "**",
       "last_name": "**"
     },
     "resources": [
       {
         "type": "dashboard",
         "id": "***"
       }
     ],
     "rls": [
       {
         "clause": "NAME = 'test'"
       }
     ]
   }
   ```
   
   Everything works smoothly in 4.x version of the superset.
   
   I cannot see any docs about this but do we have to pass datasources as well 
in resources after version 5 or is this a bug?
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] 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