-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
ui: console shows forbidden errors for requests to v1/settings
#98356
Comments
This was related to #97786, which was fixed in #97940. This error appeared on v23.1-alpha.1, which did not contain the SHA that fixed the backwards compatibility issues that originally existed with multitenant session cookies. I did some testing on master to try and reproduce this, but was unable, so I think it's safe to say that #97940 fixed this. Marking as closed, but if this somehow appears on master let's reopen. |
I'm also seeing these errors on a 22.2.2 cluster, on the dashboards page. And I'm seeing it after navigating for a while, and after refreshing, so not immediately after login. |
v1/settings
This is a frontend bug where we continue requesting settings even when the user account does not have permissions to view them. The fix should be to just give up after a 403 error. |
Indeed, I'm using a user with |
Thanks for reopening, I was testing with an |
Yup, easily reproduced when the user doesn't have |
After logging in, on the home page I see periodic:
If I refresh the page, the errors are gone. So it seems to happen only on the page loaded after a login.
Jira issue: CRDB-25216
The text was updated successfully, but these errors were encountered: