Bug 249327

Summary:	Should only update modifyTimestamp/modifiersName on MODIFY ops
Product:	[Retired] 389	Reporter:	Rich Megginson <rmeggins>
Component:	Directory Server	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	1.1.0beta	CC:	andrey.ivanov, benl, jgalipea, nkinder
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
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 23:21:11 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:	495079, 512820, 690319

Description Rich Megginson 2007-07-23 18:57:39 UTC

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 17:04:45 UTC

This falls under the category of RFC correctness

Comment 5 Rich Megginson 2009-04-09 17:26:47 UTC

See also bug 453756 and bug 305131

Comment 7 Rich Megginson 2010-11-30 17:10:44 UTC

We need this for openldap parity

Comment 8 Martin Kosek 2012-01-04 13:46:27 UTC

Upstream ticket:
https://fedorahosted.org/389/ticket/129

Comment 9 Nathan Kinder 2013-03-04 23:21:11 UTC

This was fixed in 389-ds-base-1.2.11-0.1.a1.fc17.  Closing.