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

Non-super users unable to view events under Data Stream tab even with All rights to Fleet management. #126067

Closed
dikshachauhan-qasource opened this issue Feb 21, 2022 · 9 comments
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@dikshachauhan-qasource
Copy link

Kibana version:* 8.1 BC3 Kibana cloud staging environment

Browser version: Firefox
Host OS: n/a

Preconditions:

  1. 8.1 BC3 staging Kibana cloud staging environment should be available.

Build Details:

VERSION: 8.1.0-BC3
BUILD: 50346
COMMIT: 0335dd6a26ef29ae9021d0fae9347dc88f3b7d6e
ARTIFACT LINK: https://staging.elastic.co/8.1.0-bee672a6/summary-8.1.0.html
  1. Agent should be installed and streaming data under data stream tab with super user account.

image

  1. Few Integrations should be installed and used in Agent policy.

Steps to reproduce:

  • Login to kibana with super user.
  • Navigate to Stack Management and create a new role with Read only rights for Fleet & Integrations.
  • image
  • Create a new user and assign above created Role.
  • Login with newly created user account.
  • Navigate to data stream tab under Fleet.
  • Observe, data events are not available for new user.
  • Update User account rights with index privileges to logs-* and metrics-* Indices with Read value.
  • Again, Check out user account for data stream tab.

Actual Result:

  • Data at Discover Tab is available but not unser Data streams tab.

Expected Result:
As per our understanding, A user having rights to Fleet tab, should also be able to read data at Data stream tab.

Screenshot:
image

image

@dikshachauhan-qasource dikshachauhan-qasource added the bug Fixes for quality problems that affect the customer experience label Feb 21, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 21, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Feb 21, 2022
@dikshachauhan-qasource dikshachauhan-qasource added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. needs-team Issues missing a team label labels Feb 21, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Feb 21, 2022
@manishgupta-qasource
Copy link

Reviewed & mention to @jen-huang

@jen-huang jen-huang added Team:Fleet Team label for Observability Data Collection Fleet team and removed Team:Elastic-Agent-Data-Plane labels Feb 22, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@jen-huang
Copy link
Contributor

@criamico, could you take a look at this?

@joshdover
Copy link
Contributor

  • Update User account rights with index privileges to logs-* and metrics-* Indices with Read value.

I'm curious if our current query logic requires index privileges to the backing indices. We could test this by adding read index privilege for .ds-logs-* and .ds-metrics-* and see if that 'fixes' the issue. If so, we again need to revisit how this UI queries data (related to #115805).

@criamico
Copy link
Contributor

@joshdover I tested your suggestion on cloud (Latest 8.1). The admin user has some data in data streams:

Screenshot 2022-02-23 at 17 34 44

I then created a user with Fleet "All", Integrations "Read" and the index privileges that you suggested:

Screenshot 2022-02-23 at 17 37 44

Logging with this user Data streams tab is still giving an error and not showing data. The error I get is

error: "Internal Server Error"
message: "security_exception: [security_exception] Reason: action [indices:monitor/data_stream/stats] is unauthorized for user [User_Read] with roles [Read_only], this action is granted by the index privileges [monitor,manage,all]"
statusCode: 500

So we're still not granting the correct privileges.

@joshdover
Copy link
Contributor

Ah thanks for digging in, so we need to probably block this UI if the user does not have the monitor cluster privilege. I think we can follow the same design pattern that we have used for blocking the Fleet Server setup instructions.

@joshdover
Copy link
Contributor

A fix for 8.1.0 would be ideal here, but if it slips to 8.1.1 that'd be ok.

@joshdover joshdover added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Mar 7, 2022
@joshdover
Copy link
Contributor

I'm downgrading the impact here since this is really a privileges issue that we could better surface in the UI but it is not really a broken feature.

@jlind23
Copy link
Contributor

jlind23 commented Jun 21, 2023

@amolnater-qasource as stated by Josh this is a privileges issue and not a UI bug per say, so closing this

@jlind23 jlind23 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2023
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 impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

7 participants