Bug 783283 - [RFE] Add more HBAC service groups to cover commonly used service variations
Summary: [RFE] Add more HBAC service groups to cover commonly used service variations
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-01-19 20:39 UTC by Dmitri Pal
Modified: 2016-02-19 11:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-19 11:49:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dmitri Pal 2012-01-19 20:39:41 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/1712

As HBAC services are equivalent to PAM services, there is need to treat several PAM services as a single HBAC service because they are split on PAM side due to technical purposes.

We use HBAC service groups for representing multiple PAM services belonging to the same 'service'.

Find and identify commonly provided 'services' to add to default configuration of available HBAC service groups.

Comment 7 Martin Kosek 2016-02-19 11:49:48 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.