vimal8923 commented on issue #38185:
URL: https://github.com/apache/superset/issues/38185#issuecomment-4630244877

   Hi  team,
   
   I am still facing the same issue.
   
   What I have verified so far:
   
   * Guest token is generated successfully (`200 OK`)
   * Dashboard metadata API works (`GET /api/v1/dashboard/4 -> 200`)
   * Embedded dashboard API works (`GET /api/v1/dashboard/4/embedded -> 200`)
   * The dashboard iframe loads successfully
   * I am using dashboard ID (`"4"`) in the guest token resource, not the UUID
   * `GUEST_ROLE_NAME = "Gamma"`
   * I also tested with `GUEST_ROLE_NAME = "Admin"` and the issue still occurs
   * The role has `can read Dashboard`, `can read Chart`, `can read Dataset`, 
`can read Database`, `can read EmbeddedDashboard`, and `can log on Superset`
   * Guest token audience matches the Superset configuration
   
   However, the charts do not render because the datasets request fails with:
   
   ```json
   {
     "errors": [
       {
         "message": "403 Forbidden: You don't have the permission to access the 
requested resource. It is either read-protected or not readable by the server."
       }
     ]
   }
   ```
   
   Since the issue reproduces even when using the Admin role, this does not 
appear to be a role permission problem.
   
   Could you please confirm:
   
   1. Is this related to the embedded dashboard bug fixed by PR #38309?
   2. Is there any known issue in Superset 6.x where 
`/api/v1/dashboard/{id}/datasets` returns 403 for guest-token embedded 
dashboards?
   3. Are there any additional permissions or configuration requirements for 
embedded dashboards in v6?
   
   Thank you.
   


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