From users-return-2897-apmail-directory-users-archive=directory.apache.org@directory.apache.org Tue Dec 15 18:45:20 2009 Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 68984 invoked from network); 15 Dec 2009 18:45:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Dec 2009 18:45:20 -0000 Received: (qmail 97773 invoked by uid 500); 15 Dec 2009 18:45:20 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 97734 invoked by uid 500); 15 Dec 2009 18:45:19 -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 97724 invoked by uid 99); 15 Dec 2009 18:45:19 -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:45:19 +0000 X-ASF-Spam-Status: No, hits=-6.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,RCVD_IN_DNSWL_MED X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [204.80.56.9] (HELO nyslrs.osc.state.ny.us) (204.80.56.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 18:45:17 +0000 In-Reply-To: <4B27D6E0.3020702@gmail.com> X-Disclaimed: 26562 To: users@directory.apache.org Subject: Re: APACHE DS 1.5.5 Embedded - Updating multi values attributes with nulls MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006 Message-ID: From: RNakka@osc.state.ny.us Date: Tue, 15 Dec 2009 13:45:03 -0500 X-MIMETrack: Serialize by Router on SMTP/IRM/NYSLRS(Release 7.0.2FP2|May 14, 2007) at 12/15/2009 01:45:17 PM, Serialize complete at 12/15/2009 01:45:17 PM Content-Type: multipart/alternative; boundary="=_alternative 0066FD208525768D_=" --=_alternative 0066FD208525768D_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Hi, The attibuteType description is as below. email2 is our application name=20 we use, but actually while updating the ldap we use the ibm-otherEmail=20 attribute name dn:=20 m-oid=3D2.16.840.1.113730.3.2.2.1.14,ou=3DattributeTypes,cn=3Dother,ou=3Dsc= hema 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 m-usage: USER=5FAPPLICATIONS The behaviour is same for all other multivalues attributes we have=20 configured for the users in the Embedded LDAP The LDAP context is initialised with below parameters. In Spring LDAP we=20 use the class DirContextOperations for context, Spring does the=20 initialisation for us with below parameters. local.ldap=3DAPACHEDS local.ldap.url=3Dldap://localhost:20389 local.ldap.base=3Ddc=3Dportal,dc=3Dosc,dc=3Dstate,dc=3Dny,dc=3Dus local.ldap.basedn=3Duid=3Dadmin,ou=3Dsystem local.ldap.password=3Dsecret Ramesh Nakka Websphere Portal Consultant Mobile# 1-248 835 9758 Office# 1-518-408-4457 rnakka@osc.state.ny.us rameshbabu=5Fnl@yahoo.com Emmanuel L=8Echarny =20 12/15/2009 01:35 PM Please respond to users@directory.apache.org To users@directory.apache.org cc Subject Re: APACHE DS 1.5.5 Embedded - Updating multi values attributes with nulls RNakka@osc.state.ny.us a =E9crit : > Hi Emmanuel, > > The Context is actually initialised, but here I depicted just for=20 > illustration purposes. We have a context initialised by Spring and we=20 use > the initialised context. >=20 How is it initialized ? Which is the base ? > email2 is a multi values User attribute which we use to store secondary=20 > email ids for a user=20 >=20 Can you provide the AttributeType description for this email2 element ? Notice: This communication, including any attachments, is intended solely=20 for the use of the individual or entity to which it is addressed. This=20 communication may contain information that is protected from disclosure=20 under State and/or Federal law. Please notify the sender immediately if=20 you have received this communication in error and delete this email from=20 your system. If you are not the intended recipient, you are requested not=20 to disclose, copy, distribute or take any action in reliance on the=20 contents of this information. --=_alternative 0066FD208525768D_=--