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 1676772 - [RFE] Include autounmembering feature in IPA
Summary: [RFE] Include autounmembering feature in IPA
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: rc
: 7.7
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On: 1438144
Blocks: 1647919
TreeView+ depends on / blocked
 
Reported: 2019-02-13 07:48 UTC by Martin Kosek
Modified: 2019-08-06 13:09 UTC (History)
22 users (show)

Fixed In Version: ipa-4.6.5-2.el7
Doc Type: Enhancement
Doc Text:
Clone Of: 1438144
Environment:
Last Closed: 2019-08-06 13:09:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2241 0 None None None 2019-08-06 13:09:46 UTC

Description Martin Kosek 2019-02-13 07:48:52 UTC 
+++ This bug was initially created as a clone of Bug #1438144 +++

1. Proposed title of this feature request
---> Include autounmembering feature in IPA

2. Who is the customer behind the request?
[...]

3. What is the nature and description of the request?

---> Customer wants to include a feature to autoumember, same as we have automembering in IPA.

4. Why does the customer need this? (List the business requirements here)

If username user1 has LDAP departmentnumber=City - we want to add a user to group CityUsers. This works great using automembering rules.

When user departmentnumber changes someday and departmentnumber=AnotherCity. We would like to add user to group AnotherCityUsers. But user remains to be member of group CityUsers! We would like to user to be automatically removed from the old CityUsers group.


5. How would the customer like to achieve this? (List the functional
requirements here)

---> Add a feature in IPA to automatically remove membership

[...]

--- Additional comment from Martin Kosek on 2018-12-14 14:01:21 UTC ---

As there is a risk of breaking existing behavior, when unmembering did not happen, I think there should be a configuration. It may be turned on by default, but having could save some customers that rely on unmembering to not happen.

--- Additional comment from  on 2018-12-14 18:01:34 UTC ---

(In reply to Martin Kosek from comment #22)
> As there is a risk of breaking existing behavior, when unmembering did not
> happen, I think there should be a configuration. It may be turned on by
> default, but having could save some customers that rely on unmembering to
> not happen.

Done!  Set to "on" by default

--- Additional comment from  on 2019-01-14 15:35:54 UTC ---

Fixed upstream:

https://pagure.io/389-ds-base/issue/50077

--- Additional comment from  on 2019-01-14 15:58:49 UTC ---

Design doc:

https://www.port389.org/docs/389ds/design/automember-postop-modify-design.html

--- Additional comment from Martin Kosek on 2019-02-13 07:44:02 UTC ---

I will clone this BZ also for ipa component, to make sure that any missing integration or testing is added.
Comment 4 Kaleem 2019-05-20 07:41:41 UTC 
Verified with following version of IPA/389-ds-base

[root@master ~]# rpm -q ipa-server 389-ds-base
ipa-server-4.6.5-8.el7.x86_64
389-ds-base-1.3.9.1-7.el7.x86_64
[root@master ~]# 

Please find the attached console output of automation executed locally.
Comment 6 Florence Blanc-Renaud 2019-06-06 16:57:05 UTC 
Tests added with following commits on master and ipa-4-7 branch:

master:
    https://pagure.io/freeipa/c/1d03afc908d7135609e2777de3fa6f9dcc9de9ed Tests for autounmembership feature
ipa-4-7:
    https://pagure.io/freeipa/c/eb009d6f103f1c74f131161fb60a9e6ba2b4967f Tests for autounmembership feature

Tests are in ipatests/test_integration/test_automember.py
Comment 8 errata-xmlrpc 2019-08-06 13:09:30 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/RHBA-2019:2241
Note You need to log in before you can comment on or make changes to this bug.