determine edir object creation time

Hi,

What is the reliable way to determine edir object creation time?

  • createTimeStamp -> gets updated when object is moved (verified via LDAP)
  • query:readObject($srcQueryProcessor, '', $dn, 'User', 'creatorsName')/attr[@attr-name='creatorsName']/value/@timestamp -> gets updated when object is moved (verified via IDM)
  • any attribute (verified in iMonitor) gets a new timestamp as well when object is moved

 verified in:

Product Version: eDirectory for Linux x86_64 v9.2.4 [DS] / Binary Version: 40205.00

on SUSE Linux Enterprise Server 12 SP5

(as I am not an edir sme, I might do something wrong)

Regards,

N.

Tags:

Parents
  • To my understanding, the problem is that a move is not really a move but a clone and delete (and the clone will have updated timestamps).

    As far as I recall from my ATT Times, as long as the move is in progess, you have 2 objects (old and clone) and both have the obituary-processing until all servers are happy with the change, then the old will be deleted from DIB.

    Create yourself an IDM driver to duplicate creationTimestamp from the object into a custom attribute for operation add (and for rollout on sync) to save the date.

    When there is an object move, the IDM driver cache will represent it as a move, not as an add/delete, so your driver will not update the custom attribute when moving the object.

    Hope it helps to get along

    Steffen

Reply
  • To my understanding, the problem is that a move is not really a move but a clone and delete (and the clone will have updated timestamps).

    As far as I recall from my ATT Times, as long as the move is in progess, you have 2 objects (old and clone) and both have the obituary-processing until all servers are happy with the change, then the old will be deleted from DIB.

    Create yourself an IDM driver to duplicate creationTimestamp from the object into a custom attribute for operation add (and for rollout on sync) to save the date.

    When there is an object move, the IDM driver cache will represent it as a move, not as an add/delete, so your driver will not update the custom attribute when moving the object.

    Hope it helps to get along

    Steffen

Children
No Data