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

Write tests to ensure that stack monitoring functions correctly under different kibana perms #29661

Closed
cachedout opened this issue Jan 30, 2019 · 3 comments
Assignees
Labels
Team:Monitoring Stack Monitoring team tests_needed

Comments

@cachedout
Copy link
Contributor

Recently an issue has surfaced wherein it is possible for a monitoring cluster and a production cluster to both have a valid license but for the stack monitoring application to be unable to determine if a license is valid.

image

This seems to happen in cases where there is a mismatch between the Kibana's user's role which has cluster:monitor privileges set versus a monitoring user's role which has the tighter cluster:monitor/main privilege set.

To ensure we test this appropriately, we believe that we should set the xpack.monitoring.elasticsearch.username to a user with the monitoring_user role across the board in the test runner for all functional and API tests.

@cachedout cachedout added the Team:Monitoring Stack Monitoring team label Jan 30, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring

@ycombinator
Copy link
Contributor

Related: elastic/elasticsearch#38060

@chrisronline
Copy link
Contributor

This is done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Monitoring Stack Monitoring team tests_needed
Projects
None yet
Development

No branches or pull requests

4 participants