Bug 1914713 - Unable to view config reports for some hosts when an admin user has assigned any role with limit filter
Summary: Unable to view config reports for some hosts when an admin user has assigned ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Reporting
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-11 00:54 UTC by Hao Chang Yu
Modified: 2023-09-18 00:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-28 18:02:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31602 0 Normal New Unable to view config reports for some hosts when an admin user has assigned any role with limit filter 2021-02-10 02:01:06 UTC

Description Hao Chang Yu 2021-01-11 00:54:30 UTC
Description of problem:
If an admin user have multiple roles that are assigned through one or more usergroups (mapped with LDAP groups) and any of the assigned roles has limit filter, then the admin user is unable to see the config reports of some hosts not matching the limit filter.

Steps to Reproduce:
1. Create a role, e.g. "my_role".
2. Create a filter for "my_role" and add "view_hosts" permission to it.
3. Limit the filter to "name != host1.example.com"
4. Create a usergroup, e.g. "my_usergroup"
5. Assign an admin user to "my_usergroup" and assign "my_role" to my_usergroup
6. Login as the admin user
7. Go to the Web UI -> Monitor -> Config Management -> Filter "host = host1.example.com"


Actual results:
host1.example.com is not found

Expected results:
host1.example.com should be shown regardless of the limit filter because the user is an admin user.

Comment 4 Brad Buckingham 2022-09-02 20:25:18 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 5 Brad Buckingham 2022-09-02 20:31:56 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Brad Buckingham 2022-10-28 18:02:59 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 7 Red Hat Bugzilla 2023-09-18 00:24:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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