RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 826748 - [RFE] Improve HBAC usability by preventing potential lockout
Summary: [RFE] Improve HBAC usability by preventing potential lockout
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Kosek
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-30 21:49 UTC by Dmitri Pal
Modified: 2016-02-19 12:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-19 12:03:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dmitri Pal 2012-05-30 21:49:09 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2263

We currently have one HBAC rule that allows all access. To define a set of rules for the set of the dedicated machines, say web servers of DB hosts one has to tern it off and define riles for the machines he is interested in. But he also needs to define the rule for the rest of the machines or at least for IPA server otherwise even admins would be prevented from logging into IPA hosts. To prevent this situation I suggest in addition to existing HBAC rule we should add another default rule that would allow administrator's group access to the IPA replicas. This means that we also need to have a default and automatically populated host group called "IdM Servers" (or like). This host group should be automatically maintained (replicas should be added to it) when they are prepared or installed (TBD when it is better to do it).

The scope of work:
 1. Have a default host group for replicas created when the first IPA server is installed
 2. Host group is automatically updated when replicas are added. Replica removal might be left to administrator
 3. Have a default HBAC rule that would allow Admin user group full access to the host group defined above.

Comment 2 Martin Kosek 2016-02-19 12:03:59 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker long time ago (see link to the upstream ticket above), but it was unfortunately not given a priority neither in the upstream project, nor in Red Hat Enterprise Linux.

Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.

To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Trac ticket to expedite the solution.


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