directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DIRSERVER-2145) A BIND request will do 2 lookups of the entry trying to bind
Date Tue, 23 Jan 2018 07:26:03 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Lecharny updated DIRSERVER-2145:
-----------------------------------------
    Fix Version/s:     (was: 2.0.0-M24)
                   2.0.0-M25

> 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
>            Priority: Major
>             Fix For: 2.0.0-M25
>
>
> 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
(v7.6.3#76005)

Mime
View raw message