>> Can I reasonably assume that this op attribute is available in all >> major LDAPv3 compatible directory servers, and that its behaviour >> would be consistent across them? RFC 4512 doesn't exactly mandate >> modifyTimeStamp. > > No. You can assume very little about LDAP servers in general, since > LDAP is so flexibly defined and deployed. > > For example, services that are actually about something else but provide > LDAP as an access protocol, may not bother to deal with all aspects of > LDAP. > > Then there are applications like the OpenLDAP's passwd demo backend: It > provides an LDAP view of /etc/passwd, which does't _have_ any per-entry > timestamps to publish.
Thank you for clarifying this. I decided to devise a route that first tries to use modifyTimeStamp and if not available falls back to comparison mode. I suspect for my particular application the fall back wouldn't come to use, but still it's wise to have that option. - Hide quoted text - Vladimir -- Vladimir Dzhuvinov :: software.dzhuvinov.com
