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

Re: Problems with boolean in schema



Rodrigo Costa wrote:
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?

Go and re-read the ldif(5) manpage.

Spaces are not allowed in the attributename. You have "attributename <space> <colon>" and there should be no space before the colon.

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/