-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Management app shows the sections that are not allowed by the current user capabilities #90770
Labels
bug
Fixes for quality problems that affect the customer experience
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Comments
azasypkin
added
bug
Fixes for quality problems that affect the customer experience
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
labels
Feb 9, 2021
Pinging @elastic/kibana-app (Team:KibanaApp) |
What changed recently to introduce all of this flakiness? This was solid when first introduced in 7.10 🙁 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Kibana version: 7.10.0+
Describe the bug:
While investigating flaky tests in #90576 we noticed that sometimes Management app displays sections that it shouldn't and full page refresh fixes that.
Steps to reproduce:
superuser
role) and user B (withkibana_admin
role).Ingest
sectionIngest
section. It shouldn't be shown, check the latest/capabilities
response in the Dev Tools and make sure that all "apps" are set tofalse
foringest
.Ingest
section is no longer displayed.Screenshots (if relevant): (Kibana 7.11 in Cloud)
Any additional context:
It's not immediately clear where the issue is exactly, but I'd like to make sure that Management app correctly analyzes user capabilities first. I noticed that you check capabilities in
start
, but it may become a problem in the future when we eliminate full page refresh on login/logout steps.cc @pheyos @jportner
The text was updated successfully, but these errors were encountered: