From users-return-2898-apmail-directory-users-archive=directory.apache.org@directory.apache.org Tue Dec 15 18:55:12 2009 Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 74105 invoked from network); 15 Dec 2009 18:55:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Dec 2009 18:55:12 -0000 Received: (qmail 22899 invoked by uid 500); 15 Dec 2009 18:55:11 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 22837 invoked by uid 500); 15 Dec 2009 18:55:11 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 22827 invoked by uid 99); 15 Dec 2009 18:55:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 18:55:10 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com designates 209.85.219.225 as permitted sender) Received: from [209.85.219.225] (HELO mail-ew0-f225.google.com) (209.85.219.225) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 18:55:04 +0000 Received: by ewy25 with SMTP id 25so184446ewy.25 for ; Tue, 15 Dec 2009 10:54:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=mSmosKGaOw88jzthirvKZetzbAajoPZVkY6TMW7iH5w=; b=Nyd7bKmrSxYhPxVeir/CbqCEGkxRXm97AUQIcSHlulM0UTXAC/SF9FbmhDm8oixxpP 9VWMwfuXgC+RJR3dnKKF3yokeWFs9AjihBR6tWcdnfeR7brCbzQtdAKe/Qzz7KjhV8mu SGjkID5l+5RXa5PV/JOCnL1GYLuLvTsJcG8R8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=rl+UjKyFDxwBVLKl44mKhTDORJ+qECdmwMRMcz0VlxiMbv0TUBedLiH1ssQLDzaYXk BnVNMWZQLlrSTV7263W1W9ZYUqijQdAWObYFPF2nAWosfpV7sjNdbJAGREprF+tgZbG6 Ry5XGJVSbBumSbZemChItI8GW5kYpTXJSOuh0= Received: by 10.213.0.151 with SMTP id 23mr5609632ebb.43.1260903283686; Tue, 15 Dec 2009 10:54:43 -0800 (PST) Received: from emmanuel-lecharnys-MacBook-Pro.local (lon92-10-78-226-4-211.fbx.proxad.net [78.226.4.211]) by mx.google.com with ESMTPS id 5sm6641849eyf.10.2009.12.15.10.54.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 15 Dec 2009 10:54:42 -0800 (PST) Message-ID: <4B27DB71.4000700@gmail.com> Date: Tue, 15 Dec 2009 19:54:41 +0100 From: =?UTF-8?B?RW1tYW51ZWwgTMKOY2hhcm55?= User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: APACHE DS 1.5.5 Embedded - Updating multi values attributes with nulls References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit RNakka@osc.state.ny.us a écrit : > Hi, > > The attibuteType description is as below. email2 is our application name > we use, but actually while updating the ldap we use the ibm-otherEmail > attribute name > > > > dn: > m-oid=2.16.840.1.113730.3.2.2.1.14,ou=attributeTypes,cn=other,ou=schema > objectClass: metaTop > objectClass: metaAttributeType > objectClass: top > m-collective: FALSE > m-description: user groups > m-equality: caseIgnoreMatch > m-name: ibm-otherEmail > m-nousermodification: FALSE > m-obsolete: FALSE > m-oid: 2.16.840.1.113730.3.2.2.1.14 > m-singlevalue: FALSE > m-syntax: 1.3.6.1.4.1.1466.115.121.1.15 > The 1.3.6.1.4.1.1466.115.121.1.15 syntax does not allow you to store null values into the entry, per RFC 4517, 3.3.6 : "A value of the Directory String syntax is a string of **one** or more arbitrary characters from the Universal Character Set (UCS) [UCS]. A zero-length character string is not permitted. The LDAP-specific encoding of a value of this syntax is the UTF-8 encoding [RFC3629] of the character string. Such encodings conform to the following ABNF: DirectoryString = 1*UTF8 The rule is defined in [RFC4512]. Example: This is a value of Directory String containing #!%#@. Servers and clients MUST be prepared to receive arbitrary UCS code points, including code points outside the range of printable ASCII and code points not presently assigned to any character. Attribute type definitions using the Directory String syntax should not restrict the format of Directory String values, e.g., by requiring that the character string conforms to specific patterns described by ABNF. A new syntax should be defined in such cases. The LDAP definition for the Directory String syntax is: ( 1.3.6.1.4.1.1466.115.121.1.15 DESC 'Directory String' )..." You should use another Syntax, like IA5 String (1.3.6.1.4.1.1466.115.121.1.26) which allows null values.