Bug 443241
| Summary: | memberOf: Fixup task does not fix memberOf attribute of indirect groups | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] 389 | Reporter: | Andrey Ivanov <andrey.ivanov> | ||||
| Component: | Server - memberOf Plug-in | Assignee: | Nathan Kinder <nkinder> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Chandrasekar Kannan <ckannan> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 1.1.0 | CC: | benl, rmeggins | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-08-04 18:21:14 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 249650, 452721 | ||||||
| Attachments: |
|
||||||
|
Description
Andrey Ivanov
2008-04-19 17:11:01 UTC
Created attachment 308743 [details]
CVS Diffs
The proposed approach of removing the memberOf attribute and then just
generating the proper values seems to work well. This approach makes no
assumptions about the state of the entry prior to the fixup task, which is a
good thing.
Do you need to worry about deleted attributes and values? (In reply to comment #2) > Do you need to worry about deleted attributes and values? Do you mean the values of the memberOf attribute that we're deleting as part of step 1? We don't need to worry about those since we generate all correct values by going through all of the present member attribute values in the directory. The memberOf values must be considered to be server maintained if you are using the memberOf plug-in. If someone manually added a memberOf attribute value that has no corresponding member attribute value in the group entry, then it should be removed. I mean that slapi_entry keeps track of the deleted attributes and the deleted values of an attribute - for replication urp purposes - do you have to worry about those? (In reply to comment #4) > I mean that slapi_entry keeps track of the deleted attributes and the deleted > values of an attribute - for replication urp purposes - do you have to worry > about those? I don't think I need to worry about them. If you are using the memberOf plug-in with MMR, the memberOf attribute must be fractionally excluded from replication (and will be doc'd as such). Due to this configuration, there will be no chance for a replication conflict due to the memberOf attribute itself. Checked into ldapserver (HEAD). Thanks to Rich for the review! Checking in memberof.c; /cvs/dirsec/ldapserver/ldap/servers/plugins/memberof/memberof.c,v <-- memberof.c new revision: 1.8; previous revision: 1.7 done An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0643.html |