Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Wed, 18 May 2016 06:30:13 +0000 (UTC)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12970647.1463552996000.220823.1463553013939@Atlassian.JIRA>
In-Reply-To: <JIRA.12970647.1463552996000@Atlassian.JIRA>
References: <JIRA.12970647.1463552996000@Atlassian.JIRA> <JIRA.12970647.1463552996296@arcas>
Subject: [jira] [Created] (DIRSERVER-2145) A BIND request will do 2 lookups
 of the entry trying to bind
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 18 May 2016 06:30:15 -0000

Emmanuel Lecharny created DIRSERVER-2145:
--------------------------------------------

             Summary: A BIND request will do 2 lookups of the entry trying to bind
                 Key: DIRSERVER-2145
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2145
             Project: Directory ApacheDS
          Issue Type: Improvement
    Affects Versions: 2.0.0-M21
            Reporter: Emmanuel Lecharny
             Fix For: 2.0.0-M22


When we process a {{BindRequest}}, we first fetch the principal :

{noformat}
    public void handleSimpleAuth( LdapSession ldapSession, BindRequest bindRequest ) throws Exception
    {
    ...
                principalEntry = directoryService.getAdminSession().lookup( bindRequest.getDn() );
    ...
{noformat}

then we do the actual bind :

{noformat}
    ...
            directoryService.getOperationManager().bind( bindContext );
    ...
{noformat}

At this point, we have not kept a trace of the entry we just fetched previously. This is a waste of CPU...


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)