[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Fw: Compatibility problems
please stay on the list.
> why is myAppl not a valid OID ?
because an OID must be a sequence of digits separated by dots:
1.23.456.7
0.1.2.3
but not
01.04.XXX
p.
> ----- Original Message -----
> From: "Pierangelo Masarati" <ando@sys-net.it>
> To: "anis" <anbenham@web.de>
> Cc: <openldap-software@openldap.org>
> Sent: Thursday, July 22, 2004 7:51 AM
> Subject: Re: Fw: Compatibility problems
>
>
>
>> Hi,
>>
>> we have updated yesterday our Linux Server from Suse 9.0 to Suse 9.1,
>> and
>> we
>> have tried to migrate our until now running LDAP based authentication
>> service. And this is the result:
>>
>> M1RRZSLINUX02:/etc/openldap/LAIF2 # ldapmodify -x -a -D
>> "cn=Admin,dc=my-domain,dc=com" -W -f Initial2.ldif
>> Enter LDAP Password:
>> adding new entry "id=myAppl,ou=Appl,ou=bere,dc=my-domain,dc=com"
>> ldapmodify: update failed: id=myAppl,ou=Appl,ou=bere,dc=my-domain,dc=com
>> ldap_add: Invalid DN syntax (34)
>> additional info: invalid DN
>>
>>
>>
>> The same LDIF--File has worked under Suse 9.0 containing OpenLDAP
>> 2.1.22,
>> und doesen´t work now under OpenLDAP 2.2.6.
>>
>>
>>
>> Here´s my Schema:
>>
>> attributetype ( 1.3.6.1.4.1.12345.1.2.1.1.8
>> NAME 'id'
>> DESC 'ID'
>> EQUALITY objectIdentifierMatch
>> SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
>
> "id" has syntax OID (and objectIdentifierMatch EQUALITY rule);
> "myAppl" is not a valid OID. So the DN is invalid per syntax.
>
> --
> Pierangelo Masarati
> mailto:pierangelo.masarati@sys-net.it
>
>
> SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497
>
>
--
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497