In our application, we wish to keep track of the time an account being
modified *by users*.
Currently openldap maintain a 'hidden' attribute
"modificationTimeStampe" which does exactly the same thing and updated
by openldap, recording the time of modification in Generalized Time
format. We cannot use "modificationTimeStampe" because the other
application running on the same LDAP repository updates the account
everytime this account logs in (in order to store the login time), thus
touching the 'modificationTimeStampe' even *no user modified it*.
Personally I don't like that application because I don't think LDAP
should be updated that frequently, but anyway my application has to have
a way to store different modification. Thus I used a special attribute I
defined: "myappLastModifiedTime" and update this attribute by my
application (not the LDAP server) each time the administrator modify the
account *using my application*.
After had a look into pilot object class in RFC 1274 I find it is useful
for my application:
pilotObject OBJECT-CLASS
SUBCLASS OF top
MAY CONTAIN {
info,
photo,
manager,
uniqueIdentifier,
lastModifiedTime,
lastModifiedBy,
dITRedirect,
audio}
It is being said:
# The Last Modified Time attribute type specifies the last time, in UTC
# time, that an entry was modified. Ideally, this attribute should be
# maintained by the DSA.
We are using openldap and I think in this case openldap is the DSA. My
question is: is it okay for my application to use this attribute to
store modification time? I am pretty sure no more other application will
run on this LDAP repository and I wish to define less special attributes
in order to make my application less complicated and ease administration
work (so they don't have to import my special schema file).
any suggestions?
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
