You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2018/08/17 23:00:01 UTC
[jira] [Updated] (DIRSERVER-2145) A BIND request will do 2 lookups
of the entry trying to bind
[ 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.AM25)
2.0.0.AM26
> 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.AM26
>
>
> 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)