Re: [389-users] openldap ldif to 389.
The attribute entryUUID is server assigned, and is the same as the nsUniqueId attribute in
389. You should remove that attribute from the ldif before importing.
Terry
--
Terry Soucy, Systems Analyst Information Technology Services
University of New Brunswick, Fredericton Campus http://www.unbf.ca/its
Voice: 506.447.3018 Fax: 506.453.3590 E-mail: terry.soucy(a)unb.ca
** ITS is a scent-reduced workplace - www.unbf.ca/its/policies **
On 2012-02-02, at 4:57 PM, Dan H. Eicher wrote:
I'm trying to import an ldif that was created from openldap and importing it in to
389-ds by using import database from the 389-console.
When I look at my rejects file I see the following error (multiple times):
The error was sent by the server: "Object Class Violation Attribute entryuuid
not allowed".
I did find this nugget on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=220222
(No support for RFC 4530 entryUUID attribute - from 01/04/2012)
-and- This bit of wisdom on syncing between openldap and 389:
http://directory.fedoraproject.org/wiki/Howto:OpenldapIntegration
But, I didn't find any advice for importing an ldif that uses this attribute.
Any advice from a veteran would be appreciated.
Dan
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users