You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GET api for embedded dashboard started giving 404 Not Found after adding can_read Dashboard permission to Public Role for embedded dashboard to work
#26678
Closed
mounikabtmt opened this issue
Jan 19, 2024
· 0 comments
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 am curious to know why its failing for GET.
Please help!
References:
@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.
1st call to get token:
POST http://localhost:9000/api/v1/security/login
data: {
username: "admin",
password: "admin_password",
refresh: true,
provider: "db"
}
output: access-token
2nd call to get the created created embedded dashboard id which is already created before
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 am curious to know why its failing for GET.
Please help!
References:
@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.
Originally posted by @RashmiApine in #18814 (reply in thread)
The text was updated successfully, but these errors were encountered: