Bug 797568 - [RFE] Deprecated default ipa user in cn=ipaconfig
Summary: [RFE] Deprecated default ipa user in cn=ipaconfig
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-02-26 18:11 UTC by Dmitri Pal
Modified: 2016-02-19 11:50 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Dmitri Pal 2012-02-26 18:11:29 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2442

We would rather use automember to define the default users group. If we left this setting in cn=ipaconfig we would have to try to keep it in sync with the automember rule and that would seem like a very fragile link.

Instead we'll drop this setting from cn=ipaconfig and use automember instead.

Upgrades will need to create a default automember rule using the setting from cn=ipaconfig.

Comment 2 Martin Kosek 2016-02-19 11:50:43 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.