Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Comments

@mounikabtmt
Copy link

mounikabtmt commented Jan 19, 2024

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

Originally posted by @RashmiApine in #18814 (reply in thread)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant