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

Alerts and Actions empty view in 7.11 #88624

Closed
arisonl opened this issue Jan 18, 2021 · 6 comments · Fixed by #88727
Closed

Alerts and Actions empty view in 7.11 #88624

arisonl opened this issue Jan 18, 2021 · 6 comments · Fixed by #88727
Assignees
Labels
blocker bug Fixes for quality problems that affect the customer experience REASSIGN from Team:Core UI Deprecated label for old Core UI team Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@arisonl
Copy link
Contributor

arisonl commented Jan 18, 2021

Version:
7.11

Deployment:
Elastic Cloud: europe-west1 (Belgium)

Describe the bug:
Alerts and Actions view empty despite the user having the required privileges to access it.

Screenshot 2021-01-18 at 19 43 31

Steps to reproduce:

  1. Create a role with the following privileges:
  • Elasticsearch: All cluster, all to * index
  • Kibana: All base privileges, to all applications in the default space (except ML and Stack Monitoring by default)
  1. Assign the role to a user and try access the Alerts and Actions management view as that user.

Screenshot 2021-01-18 at 19 51 07

Expected behavior:
User should have access to the Alerts and Actions management view. If they did not have the right privileges, they should not be able to access the navbar entry point.

Errors in browser console (if relevant):
Screenshot 2021-01-18 at 16 07 41
Screenshot 2021-01-18 at 16 07 59

For your attention: @legrego @gmmorris @joshdover

@arisonl arisonl added bug Fixes for quality problems that affect the customer experience Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! REASSIGN from Team:Core UI Deprecated label for old Core UI team Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jan 18, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core-ui (Team:Core UI)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@legrego
Copy link
Member

legrego commented Jan 19, 2021

I think the root cause is an API call to /api/features, which was introduced via #81876.

@elastic/kibana-alerting-services this specific API is only callable by users with the "Global All" Kibana Privilege. Users with a subset of privileges are not currently authorized to hit this endpoint.

@arisonl arisonl removed the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Jan 19, 2021
@rashmivkulkarni
Copy link
Contributor

Note: We may have to make the end to end test which currently runs as administrator to tweak it and use a specific user with limited privileges to cover this scenario.

@ymao1 ymao1 self-assigned this Jan 19, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker bug Fixes for quality problems that affect the customer experience REASSIGN from Team:Core UI Deprecated label for old Core UI team Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants