Return-Path: 
 <api-return-441-apmail-directory-api-archive=directory.apache.org@directory.apache.org>
X-Original-To: apmail-directory-api-archive@minotaur.apache.org
Delivered-To: apmail-directory-api-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 76CB910209
	for <apmail-directory-api-archive@minotaur.apache.org>;
 Thu,  9 Jan 2014 03:28:46 +0000 (UTC)
Received: (qmail 78053 invoked by uid 500); 9 Jan 2014 03:28:45 -0000
Delivered-To: apmail-directory-api-archive@directory.apache.org
Received: (qmail 77976 invoked by uid 500); 9 Jan 2014 03:28:44 -0000
Mailing-List: contact api-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:api-help@directory.apache.org>
List-Unsubscribe: <mailto:api-unsubscribe@directory.apache.org>
List-Post: <mailto:api@directory.apache.org>
List-Id: <api.directory.apache.org>
Reply-To: api@directory.apache.org
Delivered-To: mailing list api@directory.apache.org
Received: (qmail 77955 invoked by uid 99); 9 Jan 2014 03:28:42 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jan 2014 03:28:42 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of ayyagarikiran@gmail.com
 designates 74.125.82.53 as permitted sender)
Received: from [74.125.82.53] (HELO mail-wg0-f53.google.com) (74.125.82.53)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jan 2014 03:28:37 +0000
Received: by mail-wg0-f53.google.com with SMTP id k14so2270403wgh.20
        for <multiple recipients>; Wed, 08 Jan 2014 19:28:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:content-type;
        bh=yi/52pqQvtVlidlFgbVeA3ysRAAD/0MHOLlGQ5ga5do=;
        b=OpFHeI/ZNf+EYYLeYaerOAJZhmZ2LYwXtShKmNAvMPVEd9O07ENRScX6Jd7lH2Y7vM
         zBjwIM8unZMXMlhgcpYDmGWoPbGNy+FK5OsKtExAZo8VrTInzmuVDMlQdw6UP8YIvrru
         INGJ20aMSNU7cf6KEA7lIG86cuL34f/dz99rxhLNkYpmnDsHTTjkSTjFWSGYoABVQMXw
         WKMpBo8rs5otTuWqpm4wNtDGu2T1wafbL0GpwL0Il3FWyyV97sObcOsugIsBLVWghnVS
         aqd+LlacUIejEr4qBmZgkIcTDRkBNUpJ8A4+qx10wQdy2V0/vRT767gUiXG2C7ufWdaX
         WfZw==
MIME-Version: 1.0
X-Received: by 10.194.80.137 with SMTP id r9mr550898wjx.88.1389238095603; Wed,
 08 Jan 2014 19:28:15 -0800 (PST)
Sender: ayyagarikiran@gmail.com
Received: by 10.216.166.194 with HTTP; Wed, 8 Jan 2014 19:28:15 -0800 (PST)
In-Reply-To: 
 <CAGPFiXOYQKG=OwTXqRfiud6mWevV7YyeHZi=iEDz3UChHPYE2g@mail.gmail.com>
References: 
 <CAGPFiXOYQKG=OwTXqRfiud6mWevV7YyeHZi=iEDz3UChHPYE2g@mail.gmail.com>
Date: Thu, 9 Jan 2014 08:58:15 +0530
X-Google-Sender-Auth: 7vgfza88d4JVgbnl1yaGSdz7Ikc
Message-ID: 
 <CABzFU-f6Wou48E_E2rHcAb+oHzdiRgYZ6=f5djxnYfSVsdsWvA@mail.gmail.com>
Subject: Re: possible bugwhen adding {sha} password
From: Kiran Ayyagari <kayyagari@apache.org>
To: api@directory.apache.org, users@directory.apache.org
Content-Type: multipart/alternative; boundary=047d7bdc8e86326db604ef81333e
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7bdc8e86326db604ef81333e
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jan 9, 2014 at 6:54 AM, Flavio Mattos <flaviomattos86@gmail.com>wrote:

> Hi everyone!
>
> I have noticed a strage behavior/bug using the client API when I try to
> create entries with encrypted password using {SHA}.
> I am invoking the method the following constructor:
>
>
> What is happening is: For some reason the API is adding a "'" for a few
> entries. To make sure the problem is not with my code I have tried to use a
> hardcoded value.
> When I go to the Apache Directory Studio the password is like this:
> '{sha}W6ph5Mm5Pz8GgiULbPgzG37mj9g=' and instead of being {sha} encrypted it
>
this is the value of the hashed password(including the hash method), what
else are you expecting?

> becomes plain text password.
> The code below is inside a loop where I add different entries..
>
> Entry entry = new DefaultEntry(dn, finalArray); //dn is a String and
> finalArray is Object[]
>
> private void addEntry(Entry entry, LdapConnection conn) throws
> LdapException {
>
>         AddRequest addRequest = new AddRequestImpl();
>         addRequest.setEntry(entry);
>         AddResponse response = conn.add(addRequest);
>
>         if
> (ResultCodeEnum.SUCCESS.equals(response.getLdapResult().getResultCode())) {
>             logger.log(Level.INFO, "Entry {0} added successfully",
> entry.getDn().getName());
>         } else {
>             logger.log(Level.SEVERE, "Error adding entry {0} {1}", new
> Object[]{entry.getDn().getName(), response.getLdapResult().getResultCode()
> + "-" + response.getLdapResult().getResultCode().getMessage()});
>             if (!
>
> response.getLdapResult().getResultCode().equals(ResultCodeEnum.ENTRY_ALREADY_EXISTS)
> ) {
>
>
> ldapExceptionManagerLocal.insert(this.createLdapSyncException(entry.getDn().getName(),
> response.getLdapResult().getResultCode().name(),
> response.getLdapResult().getResultCode().getMessage(),
> LdapSyncException.ESYNC_TYPE.WALLET));
>                 throw new
> LdapException(response.getLdapResult().getResultCode().name());
>             }
>         }
> }
>
>
>
> That is result of the toString method.
> Entry:
>     dn: uid=30,ou=customer_db,,dc=example,dc=com
>     objectclass: inetOrgPerson
>     objectclass: organizationalPerson
>     objectclass: person
>     objectclass: top
>     stateorprovincename: NY
>     postalcode: 10475
>     mail: unittest30@example.com
>     sn: Doe
>     userpassword: {sha}W6ph5Mm5Pz8GgiULbPgzG37mj9g=
>     cn: John
>     street: 999 N TEST AVE
>     givenname: John
>     localityname: UNITED STATES
>
>
> Does anybody know if there is a bug already registered for this?
>
> Thanks
>
> Flavio
>



-- 
Kiran Ayyagari
http://keydap.com

--047d7bdc8e86326db604ef81333e--