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

   1st call to get token:
   
   POST http://localhost:9000/api/v1/security/login
   
   data: {
        username: "admin",
        password: "admin",
        refresh: true,
        provider: "db"
   }
   output:  access-token 
   
   2nd call to get the created created embedded dashboard id 
   GET http://localhost:9000/api/v1/dashboard/my-dashboard/embedded 
   
   request headers: 
   
   Authorization -> Bearer {access_token}
   
   response: 
   giving embedded dashboard id which is already created before for the above 
slug
   
   -------------------------------------------------
   
   To have embedded dashboard coming, I have started adding few permissions to 
Public Role mentioned in attached discussion. 
   But when I am giving can_read Dashboard permission to Public Role, My actual 
request to get the above #2 request is getting failed with 404.
   
   Hence tried to create embedded dashboard id again for the same url-slug 
using POST operation. 
   
   Its giving same id for POST now which we are supposed to get for the GET 
request. But I want the GET request to work in all cases. 
   
   Please help!
   
   
   
   @apole I cross-checked the guest token payload and static HTML file. both 
seem to be correct. 
   Please try to add the below permission to the "public" role. Not sure it 
might be helpful or nor.
   
![IMG_1495](https://user-images.githubusercontent.com/127457378/224854989-336348dc-7a76-40a1-92dd-07913a62f95e.jpg)
   
   _Originally posted by @RashmiApine in 
https://github.com/apache/superset/discussions/18814#discussioncomment-5297238_


-- 
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