[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Problems with boolean in schema
- To: openldap-software@openldap.org
- Subject: Problems with boolean in schema
- From: Rodrigo Costa <rlvcosta@yahoo.com>
- Date: Fri, 28 Aug 2009 12:53:35 -0700 (PDT)
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1251489215; bh=PSlWM7doJTNhFUZ5QpMjZLsgsIzQR59wyDGOIBIZs8A=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=Y47bPbttNUhaIYn4vOQE9uiOT7Y+HmIlGqarjej/3yeUyt4mt+SkbMhM8LZrrW0Lo2YO/JvZI/Ia3c0e0zBsvBTTQXMmNRCchCiihU5OYjPPlmBLE8m8+yryITR4D+DQ8fV3rQPH8OMnX3DQECbzjRyalvtDeHhnsXhe/buWnes=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=smCWrKC958X8hZmDSFjybv5D7ssgqvOqyUSFHhqkc7lImIjd59ecmj7ae63P6It/6EFCPez/9N68eN84sh7pb79osN9GoI456i+gB0Jj85VojqvlWx+GaFQ8apQanSjZlL+4N++QirdDn5Duj33QR/eV3CTQdX+hSYZa2JiQqpI=;
Dear openldap community,
I'm using a boolean entrance in my DB which when I try to load using a
LDIF file I receive an error message.
The attribute definition is :
###############################
# ATTRIBUTES FOR INTERCEPTION
---------------------------------------------------------------------------
###############################
#
# isinterception
#
# tells if the admin user is authaurised to manage the interception flag
# of the user subscriptions
#
Attributetype ( 1.3.6.1.4.1.6287.300.1.112 NAME 'isinterception'
EQUALITY booleanMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
SINGLE-VALUE )
Which I double checking in RFC2252 where I have definition :
6.4. Boolean
( 1.3.6.1.4.1.1466.115.121.1.7 DESC 'Boolean' )
Values in this syntax are encoded according to the following BNF:
boolean = "TRUE" / "FALSE"
Boolean values have an encoding of "TRUE" if they are logically true,
and have an encoding of "FALSE" otherwise.
My LDIF file has the entrance(with traces during load) :
=> str2entry: "dn:
loginname=protectedaccess,ou=ADMINUSERS,ou=PROFILECONF,ou=INDEXES,o=domain,c=fr
objectclass: adminuser
objectclass: interception
loginname: protectedaccess
loginpasswd: {CRYPT}inRf5tBzmUVog
profileidlist: 100,101,102,103,104,105,106,107
sitelist: brtldpvip
mailboxgroup: 255
isinterception : TRUE
interceptprefix : 88
interceptsecretcode : 1234
interceptprofileid : 104
"
>>> dnPrettyNormal:
<loginname=protectedaccess,ou=ADMINUSERS,ou=PROFILECONF,ou=INDEXES,o=domain,c=fr>
<<< dnPrettyNormal:
<loginname=protectedaccess,ou=ADMINUSERS,ou=PROFILECONF,ou=INDEXES,o=domain,c=fr>,
<loginname=protectedaccess,ou=adminusers,ou=profileconf,ou=indexes,o=domain,c=fr>
<= str2entry: str2ad(isinterception): AttributeDescription contains
inappropriate characters
slapadd: could not parse entry (line=590)
=> str2entry: "dn:
loginname=webccuser1,ou=ADMINUSERS,ou=PROFILECONF,ou=INDEXES,o=domain,c=fr
objectclass: adminuser
loginname: webccuser1
loginpasswd: {CRYPT}ajc0hX/PgdoZM
profileidlist: 100,101,102,103,105,106,107
sitelist: brtldpvip
mailboxgroup: 255
See error above as "AttributeDescription contains inappropriate characters".
The attribute isinterception has all letters in uppercase as expected.
and I also verified for unprinted characters but I do not see anything
there. This file loads in openldap 2.3 without any problems but I could
not load without this message in 2.4.x.
Do you have any idea about what it could be?
Regards,
Rodrigo.