Bug 1090627 - [RFE][L-8] Copy EVM-Super_administrator role does not actually copy all permissions
Summary: [RFE][L-8] Copy EVM-Super_administrator role does not actually copy all permi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.2.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: MVP
: 5.10.0
Assignee: Keenan Brock
QA Contact: Nandini Chandra
URL:
Whiteboard: rbac
Depends On:
Blocks: 1555371
TreeView+ depends on / blocked
 
Reported: 2014-04-23 19:20 UTC by Bill Helgeson
Modified: 2022-03-13 13:53 UTC (History)
15 users (show)

Fixed In Version: 5.10.0.0
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 23:02:13 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1203028 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1253583 0 medium CLOSED [RFE] Customized roles can not select tags filter when creating chargeback report. 2021-02-22 00:41:40 UTC
Red Hat Knowledge Base (Solution) 2192661 0 None None None 2016-03-08 18:27:07 UTC
Red Hat Product Errata RHSA-2019:0212 0 None None None 2019-02-07 23:02:31 UTC

Internal Links: 1203028 1253583

Description Bill Helgeson 2014-04-23 19:20:49 UTC
Description of problem: When trying to create a reports using chargebacks as context an user using a new role copied from EVM-Super_administrator, this user does not have all the options on the filters tab such as to use tags.

Log off and log back in using admin user account and report can be created properly.


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


How reproducible:


Steps to Reproduce:
1. copy internal super admin role
2. connect ldap user from AD group to this role
3. try to create a chargeback report as this user
4. Try to apply a proper filter using tags - drop down will be missing.

Actual results:


Expected results:


Additional info:

Comment 3 Dan Clarizio 2014-05-06 22:02:57 UTC
Xav, we have always treated super admin special, so much so that we always allow super admin to sign in even if an external authentication system is active.  We have no real way of identifying that a role is "super", except the one we ship with the product that we identify by name.

Should this be an RFE to figure out a way to identify user created roles as super so we can allow them all of the super admin capabilities?

Comment 13 CFME Bot 2018-05-31 19:41:28 UTC
New commit detected on ManageIQ/manageiq/master:

https://github.com/ManageIQ/manageiq/commit/db76d9632ceeab8f58f8375dc8d95f864680e970
commit db76d9632ceeab8f58f8375dc8d95f864680e970
Author:     Keenan Brock <keenan>
AuthorDate: Tue May 15 16:53:19 2018 -0400
Commit:     Keenan Brock <keenan>
CommitDate: Tue May 15 16:53:19 2018 -0400

    use features to check if a role is an admin role

    the role name used to determine if it were

    https://bugzilla.redhat.com/show_bug.cgi?id=1090627
 app/models/miq_group.rb | 6 +-
 app/models/miq_product_feature.rb | 4 +-
 app/models/miq_user_role.rb | 12 +-
 app/models/user.rb | 9 +-
 db/fixtures/miq_product_features.yml | 5 +
 db/fixtures/miq_user_roles.yml | 1 +
 lib/rbac/filterer.rb | 5 +-
 spec/factories/miq_user_role.rb | 13 +-
 spec/lib/task_helpers/exports/roles_spec.rb | 2 +-
 9 files changed, 40 insertions(+), 17 deletions(-)

Comment 14 CFME Bot 2018-06-04 16:23:48 UTC
New commit detected on ManageIQ/manageiq-api/master:

https://github.com/ManageIQ/manageiq-api/commit/bf3b8020a4d71a1962df35182327b64761e4da7f
commit bf3b8020a4d71a1962df35182327b64761e4da7f
Author:     Keenan Brock <keenan>
AuthorDate: Thu May 24 19:24:19 2018 -0400
Commit:     Keenan Brock <keenan>
CommitDate: Thu May 24 19:24:19 2018 -0400

    use request_admin_user?

    the generic admin is phased out.
    Instead we are using the actual property.
    `request_admin_user?` is a shortcut for request superadmin privs

    https://bugzilla.redhat.com/show_bug.cgi?id=1090627

 app/controllers/api/automation_requests_controller.rb | 4 +-
 app/controllers/api/provision_requests_controller.rb | 4 +-
 app/controllers/api/requests_controller.rb | 4 +-
 app/controllers/api/service_requests_controller.rb | 4 +-
 spec/requests/automation_requests_spec.rb | 4 +-
 spec/requests/provision_requests_spec.rb | 6 +-
 spec/requests/requests_spec.rb | 4 +-
 spec/requests/service_requests_spec.rb | 4 +-
 8 files changed, 17 insertions(+), 17 deletions(-)

Comment 17 CFME Bot 2018-06-08 11:54:24 UTC
New commit detected on ManageIQ/manageiq-ui-classic/master:

https://github.com/ManageIQ/manageiq-ui-classic/commit/326f3f68d36e88b39a88f67580e93ef145921f73
commit 326f3f68d36e88b39a88f67580e93ef145921f73
Author:     Keenan Brock <keenan>
AuthorDate: Mon May 21 10:59:58 2018 -0400
Commit:     Keenan Brock <keenan>
CommitDate: Mon May 21 10:59:58 2018 -0400

    Use {report,request}_admin_user?

    https://bugzilla.redhat.com/show_bug.cgi?id=1090627

 app/controllers/application_controller.rb | 4 +-
 app/controllers/application_controller/current_user.rb | 6 +-
 app/controllers/chargeback_controller.rb | 2 +-
 app/controllers/configuration_controller.rb | 14 +-
 app/controllers/report_controller.rb | 2 +-
 app/controllers/report_controller/menus.rb | 6 +-
 app/controllers/report_controller/saved_reports.rb | 2 +-
 app/helpers/application_helper/button/miq_request_delete.rb | 2 +-
 app/presenters/tree_builder_report_saved_reports.rb | 4 +-
 app/views/layouts/_adv_search_body.html.haml | 2 +-
 app/views/layouts/_adv_search_footer.html.haml | 2 +-
 spec/controllers/report_controller/widget_spec.rb | 2 +-
 spec/helpers/application_helper/buttons/miq_request_delete_spec.rb | 2 +-
 13 files changed, 25 insertions(+), 25 deletions(-)

Comment 18 Keenan Brock 2018-06-08 13:56:36 UTC
Thanks all

Comment 19 Nandini Chandra 2018-07-16 22:29:19 UTC
verified in 5.10.0.4

Comment 21 errata-xmlrpc 2019-02-07 23:02:13 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/RHSA-2019:0212


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