I'm sorry Alexey, but you happen to be wrong here.
We use cn=default,ou=policies,[our root domain] without issues.
- chris
Chris Jacobs, Systems Administrator Apollo Group | Apollo Marketing | Aptimus 2001 6th Ave Ste 3200 | Seattle, WA 98121 phone: 206.839-8245 | cell: 206.601.3256 | Fax: 208.441.9661 email: chris.jacobs@apollogrp.edu
----- Original Message ----- From: openldap-technical-bounces@OpenLDAP.org openldap-technical-bounces@OpenLDAP.org To: openldap-technical@openldap.org openldap-technical@openldap.org Sent: Fri Jan 14 03:24:04 2011 Subject: Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX
Could not add object cn=default,ou=Policies,dc=itelsib,dc=com Message: Invalid syntax Error code: 0x15 (LDAP_INVALID_SYNTAX) Error description: An invalid attribute value was specified.
You can not use cn=default,ou=Policies,dc=itelsib,dc=com
please try cn=ppolicy,ou=Policies,dc=itelsib,dc=com
-----Original Message----- From: openldap-technical-bounces@OpenLDAP.org [mailto:openldap-technical-bounces@OpenLDAP.org] On Behalf Of openldap-technical-request@OpenLDAP.org Sent: Thursday, January 13, 2011 6:00 PM To: openldap-technical@openldap.org Subject: openldap-technical Digest, Vol 38, Issue 12
Send openldap-technical mailing list submissions to openldap-technical@openldap.org
To subscribe or unsubscribe via the World Wide Web, visit http://www.openldap.org/lists/mm/listinfo/openldap-technical or, via email, send a message with subject or body 'help' to openldap-technical-request@openldap.org
You can reach the person managing the list at openldap-technical-owner@openldap.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of openldap-technical digest..."
Send openldap-technical mailing list submissions to openldap-technical@openldap.org When replying, please edit your Subject: header so it is more specific than "Re: openldap-technical digest..."
Today's Topics:
1. One root and two domain? (gael therond) 2. Re: One root and two domain? (Pierangelo Masarati) 3. Re: Evolution Contacts Schema (Peter L. Berghold) 4. Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Konstantin Boyandin) 5. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Quanah Gibson-Mount) 6. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Konstantin Boyandin) 7. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Chris Jacobs) 8. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Konstantin Boyandin) 9. LDAP and PAM: account is expired, but pam_ldap allows authentification (Konstantin Boyandin) 10. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Chris Jacobs) 11. Re: LDAP and PAM: account is expired, but pam_ldap allows authentification (Indexer) 12. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Howard Chu) 13. Re: LDAP and PAM: account is expired, but pam_ldap allows authentification (Howard Chu) 14. Re: LDAP and PAM: account is expired, but pam_ldap allows authentification (Chris Jacobs) 15. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Howard Chu) 16. Re: LDAP and PAM: account is expired, but pam_ldap allows authentification (Howard Chu) 17. Re: LDAP and PAM: account is expired, but pam_ldap allows authentification (Indexer) 18. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Dieter Kluenter) 19. Re: LDAP and PAM: account is expired, but pam_ldap allows authentification (Howard Chu) 20. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Konstantin Boyandin) 21. Re: LDAP and PAM: account is expired, but pam_ldap allows authentification (Indexer) 22. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Pierangelo Masarati) 23. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Konstantin Boyandin) 24. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Howard Chu) 25. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Howard Chu) 26. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Pierangelo Masarati) 27. Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX (Howard Chu) 28. Re: Evolution Contacts Schema (Bj?rn Ruberg) 29. Re: Evolution Contacts Schema (Stefan Palme) 30. Hello, how (Alexey Shalin)
----------------------------------------------------------------------
Message: 1 Date: Wed, 12 Jan 2011 15:58:28 +0100 From: gael therond gael.therond@gmail.com To: openldap-technical openldap-technical@openldap.org Subject: One root and two domain? Message-ID: AANLkTinxG_W4QQA5-vA587CN1FtYLf7TTUUchNP1DfTh@mail.gmail.com Content-Type: text/plain; charset="utf-8"
Is it possible to add a domain on an already existing root?
I got the following root for now:
dc=lab,dc=corp
and I want to create a second Top entry on my root which will be named like this:
dc=prod,dc=corp
Is that possible?
I've try the following syntaxe without succes.
Racine.ldif:
#Racine dn: dc=prod, dc=corp ObjectClass: Top ObjectClass: dcObject ObjectClass: organization o: prod.corp dc: prod
#OU Groups dn: ou=groups, dc=prod, dc=geka ObjectClass: organizationalUnit ObjectClass: top ou: groups
#OU Users dn: ou=users, dc=prod, dc=geka ObjectClass: organizationalUnit ObjectClass: top ou: users
And then I've done the usual LdapADD command, but with the following error returned:
ldap_add: Server is unwilling to perform (53) Additional info: No global Superior Knowledge.
Well, my guest is that I didn't set correctly Slapd because my default root is lab.corp instead of being TLD .corp Is that theory right?
Many thanks