Bug 1844268 - The common user shouldn't see the system indices
Summary: The common user shouldn't see the system indices
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Periklis Tsirakidis
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1842357
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-04 22:56 UTC by OpenShift BugZilla Robot
Modified: 2020-07-13 17:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:43:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 1920 0 None open [release-4.5] Bug 1844268: Limit role project_user to access only owned kibana idx 2020-06-24 03:34:26 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:43:38 UTC

Description OpenShift BugZilla Robot 2020-06-04 22:56:41 UTC
+++ This bug was initially created as a clone of Bug #1842357 +++

Description of problem:
The common user can the system indices of all the other users.  it shouldn't.


Version-Release number of selected component (if applicable):
4.5

How reproducible:
Always

Steps to Reproduce:
1. Login kibana as common user
2. Create pattern to include system indices.
3. Discover system indices documents  

Actual results:
The common user can list .kibana.* indices of all the other users.

Expected results:
The common user should only see the index itself. Or it couldn't see any indices.

--- Additional comment from anli on 2020-06-01 05:06:15 UTC ---

Created attachment 1693991 [details]
The pattern list a a common user

Comment 3 Anping Li 2020-06-09 01:40:53 UTC
Verified on elasticsearch-operator.4.5.0-202006080457.

Comment 4 errata-xmlrpc 2020-07-13 17:43:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409


Note You need to log in before you can comment on or make changes to this bug.