I can also tell you that NSUniqueID was 19d98481-1dd211b2-8023e758-74ea0000 then changed to 647b2b01-1dd211b2-80c7e758-74ea0000 --BO
On 5/15/07, Bjorn Oglefjorn <[EMAIL PROTECTED]> wrote:
That's the problem Richard, I'm not sure how it happens. I can tell you this much though. I am using NSUniqueID as a globally unique id for a one-way sync agreement to a specific application (from FDS to the application). The requirement for the globally unique id is that it never changes. If it somehow does change, the sync process provides an error stating that the globally unique ids in FDS and the application no longer match. I can't determine exactly what is causing this change, but I do know that it is happening. --BO On 5/15/07, Richard Megginson <[EMAIL PROTECTED]> wrote: > > Bjorn Oglefjorn wrote: > > Hello all, > > > > Can someone tell me, does the NSUniqueID attribute ever change for a > > given entry in the directory? > No. > > If so (I've seen it happen), > Can you describe exactly what you saw and how to reproduce it? > > what are the criteria that prompt NSUniqeID to change? > > > > Thanks, > > BO > > > ------------------------------------------------------------------------ > > > > -- > > Fedora-directory-users mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > > -- > Fedora-directory-users mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/fedora-directory-users > > >
-- Fedora-directory-users mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-directory-users
