Bug 249327 - Should only update modifyTimestamp/modifiersName on MODIFY ops
Should only update modifyTimestamp/modifiersName on MODIFY ops
Status: CLOSED CURRENTRELEASE
Product: 389
Classification: Community
Component: Directory Server (Show other bugs)
1.1.0beta
All Linux
medium Severity high
: ---
: ---
Assigned To: Rich Megginson
Chandrasekar Kannan
:
Depends On:
Blocks: 389_1.3.0 512820 690319
  Show dependency treegraph
 
Reported: 2007-07-23 14:57 EDT by Rich Megginson
Modified: 2015-01-04 18:27 EST (History)
4 users (show)

See Also:
Fixed In Version: 389-ds-base-1.2.11-0.1.a1.fc17
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-04 18:21:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rich Megginson 2007-07-23 14:57:39 EDT
The directory server updates the modifyTimestamp on operations other than Modify
operations.  See http://tools.ietf.org/html/rfc4512.  However, attributes can be
modified by operations other than Modify.  For example, with password policy
enabled, a Bind operation may update one or more operational attributes in a
user's entry.  Admin's do not expect modifyTimestamp to be updated under this
and similar circumstances.  See also
http://www.openldap.org/its/index.cgi/Software%20Bugs?id=5040;page=2
Comment 4 Rich Megginson 2009-04-09 13:04:45 EDT
This falls under the category of RFC correctness
Comment 5 Rich Megginson 2009-04-09 13:26:47 EDT
See also bug 453756 and bug 305131
Comment 7 Rich Megginson 2010-11-30 12:10:44 EST
We need this for openldap parity
Comment 8 Martin Kosek 2012-01-04 08:46:27 EST
Upstream ticket:
https://fedorahosted.org/389/ticket/129
Comment 9 Nathan Kinder 2013-03-04 18:21:11 EST
This was fixed in 389-ds-base-1.2.11-0.1.a1.fc17.  Closing.

Note You need to log in before you can comment on or make changes to this bug.