Description of problem: Seems to be impossible to get requests list from api as a non-admin user, only admin can get requests from api. Version-Release number of selected component (if applicable): 5.9.2.4 How reproducible: Steps to Reproduce: 1. See list of request in Web portal by going to Service>Requests as non-admin user 2. make an API query to /api/requests as the same user 3. Actual results: count: shows non zero value subcount: 0 Expected results: Using web portal, request can be seen under Services>Requests, it should also show requests at /api/requests for the same user Additional info: User is in custom group with custom role having full access and no filter.
I added a product feature 'miq_request_superadmin' for viewing/creating requests in https://bugzilla.redhat.com/show_bug.cgi?id=1090627 before: only users in the default admin group (not a copy) could view requests. after: a copy of the admin group or other groups with the feature can now view requests There were a number of BZs that seemed to want the same type of solution. I tried to build that solution to solve the general solution. Please let me know if it conflicts with your needs here.
Kennan, please correct me if I'm wrong, but as far as I can tell, to have this fixed in current 5.9, we'd have to backport all of the PRs (Core + UI + API) from https://bugzilla.redhat.com/show_bug.cgi?id=1090627 over to 5.9. Seeing https://bugzilla.redhat.com/show_bug.cgi?id=1090627 is actually an RFE and would require non-trivial amount of work to be done (including rigorous testing), this needs to be re-evaluated whether or not this is a 5.9 material.
Milan, Think this can be closed - it should be in master. --K
The work here has already been done by Keenan (it's all in current master), I'm moving this over to POST so that it can be properly verified.
Appliance version: 5.10.0.32 Non-admin user can now see his requests if he has Services -> Requests -> View permission. UI is consistent with api.
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/RHSA-2019:0212