[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: AW: Invalid manager attribute when in form 1.3.6.1.4.1.1466.0=#04024869, O=Test, C=GB

On 05/23/2013 01:38 PM, Soulier, Marcel wrote:

Hi,

I think your answer does not fully explain my problem. I changed my example to use the dn 1.2.840.113549.1.9.1=#04024869, O=Test, C=GB where 1.2.840.113549.1.9.1 should be defined  as the email Attribute in core.schema. But I still get the same exception.
Right. The point is that such syntax is unsupported (see the comment in dn.c:305 

/* AVA is binary encoded, not supported */
I don't recall the reason, you may be able to dig it up in the mailing list archives (I'd suggest to first look at openldap-devel). 

p.



Marcel

-----Ursprüngliche Nachricht-----
Von: openldap-technical-bounces@OpenLDAP.org [mailto:openldap-technical-bounces@OpenLDAP.org] Im Auftrag von Pierangelo Masarati
Gesendet: Donnerstag, 23. Mai 2013 10:59
An: openldap-technical@openldap.org
Betreff: Re: Invalid manager attribute when in form 1.3.6.1.4.1.1466.0=#04024869, O=Test, C=GB

On 05/23/2013 10:19 AM, Soulier, Marcel wrote:

Hi,

I am trying to import the following ldif file into openldap and get
the error message "manager: value #0 invalid per syntax".

test.ldif:

dn: cn=test,o=users,dc=example,dc=com

objectClass: top

objectClass: person

cn: test

manager: 1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB

Console output:

adding new entry "cn=test,o=users,dc=example,dc=com"

ldap_add: Invalid syntax (21)

                  additional info: manager: value #0 invalid per syntax

According to the cosine.schema the value of the manager attribute
should have the EQUALITY distinguishedNameMatch, SYNTAX
1.3.6.1.4.1.1466.115.121.1.12

The value "1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB" is taken from the
examples provided for DN in rfc2252 and works fine in open-ds. So I
would expect it to work in openldap as well.

What am I missing?


OID 1.3.6.1.4.1.1466.0 is not defined in any of OpenLDAP's distributed schema files, nor hardcoded anywhere.  OpenLDAP does strong schema adherence checks, so it is not possible to add a DN made of undefined attributes.

p.




--
Pierangelo Masarati
Associate Professor
Dipartimento di Ingegneria Aerospaziale
Politecnico di Milano