Back to bug 1304682

Who When What Removed Added
Michele Casaburo 2016-02-04 10:53:53 UTC CC gparente
thierry bordaz 2016-02-04 12:01:56 UTC CC tbordaz
German Parente 2016-02-15 09:37:48 UTC CC nkinder, rmeggins
Component ipa 389-ds-base
Assignee ipa-maint nhosoi
QA Contact nsoman vashirov
Noriko Hosoi 2016-02-15 17:28:43 UTC Status NEW ASSIGNED
John Skeoch 2016-04-18 10:20:33 UTC CC aglotov
Noriko Hosoi 2016-06-02 20:41:46 UTC Flags needinfo?(tbordaz)
thierry bordaz 2016-06-03 07:31:38 UTC Flags needinfo?(tbordaz)
Noriko Hosoi 2016-06-30 00:07:40 UTC Status ASSIGNED POST
CC mreynolds
Doc Text Cause: Adding an entry that is rejected by multiple backend transaction plugins like "automembership"
Doc Text , and "Managed Entry"

Consequence: The entry cache is left in an inconsistent state that allows a search to return the entry was not added.

Fix: Make sure the part of the entry cache that stores the DN of the entry is properly cleaned up when an
Doc Text "add" operation fails

Result: If an entry is not added to the database because it is rejected by a plugin, that the entry does not show up in searches after it was rejected
Status POST MODIFIED
Fixed In Version 389-ds-base-1.3.5.9-1.el7
errata-xmlrpc 2016-06-30 00:35:13 UTC Status MODIFIED ON_QA
Simon Pichugin 2016-07-13 20:48:57 UTC Status ON_QA VERIFIED
CC spichugi
Petr Bokoc 2016-08-01 14:45:21 UTC CC pbokoc
Docs Contact pbokoc
Doc Text Cause: Adding an entry that is rejected by multiple backend transaction plugins like "automembership", and "Managed Entry"

Consequence: The entry cache is left in an inconsistent state that allows a search to return the entry was not added.

Fix: Make sure the part of the entry cache that stores the DN of the entry is properly cleaned up when an "add" operation fails

Result: If an entry is not added to the database because it is rejected by a plugin, that the entry does not show up in searches after it was rejected
Entries rejected by multiple plug-ins no longer show up in searches

Previously, when an entry was rejected by multiple backend transaction plug-ins (for example, *Auto Membership* and *Managed Entry*) at the same time, the entry cache was left in an inconsistent state. This allowed a search to return the entry even though it was not added. With this update, the entry cache which stores the Distinguished Name (DN) of the entry is properly cleaned up when an "add" operation fails, and rejected entries are no longer returned by "ldapsearch".
Petr Bokoc 2016-08-22 11:31:29 UTC Doc Text Entries rejected by multiple plug-ins no longer show up in searches

Previously, when an entry was rejected by multiple backend transaction plug-ins (for example, *Auto Membership* and *Managed Entry*) at the same time, the entry cache was left in an inconsistent state. This allowed a search to return the entry even though it was not added. With this update, the entry cache which stores the Distinguished Name (DN) of the entry is properly cleaned up when an "add" operation fails, and rejected entries are no longer returned by "ldapsearch".
Entries rejected by multiple plug-ins no longer show up in searches

Previously, when an entry was rejected by multiple back end transaction plug-ins (for example, *Auto Membership* or *Managed Entry*) at the same time, the entry cache was left in an inconsistent state. This allowed a search to return the entry even though it was not added. With this update, the entry cache which stores the Distinguished Name (DN) of the entry is properly cleaned up when an "add" operation fails, and rejected entries are no longer returned by "ldapsearch".
errata-xmlrpc 2016-11-02 12:24:39 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-11-03 20:39:26 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-11-03 16:39:26 UTC
Simon Pichugin 2020-09-13 21:40:24 UTC Link ID Github 389ds/389-ds-base/issues/1787

Back to bug 1304682