• State Not Answered
  • Replies replies
    7
  • Subscribers subscribers
    22
  • Views views
    1212
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

determine edir object creation time

nle

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
  • 0

    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
  • 0

    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

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.