Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 229290 - Password management inefficient entry usage
Summary: Password management inefficient entry usage
Status: CLOSED DUPLICATE of bug 184130
Alias: None
Product: 389
Classification: Retired
Component: Performance
Version: 1.0.4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Orla Hegarty
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-19 23:12 UTC by Pete Rowley
Modified: 2008-08-11 23:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-02-19 23:50:20 UTC

Attachments (Terms of Use)

Description Pete Rowley 2007-02-19 23:12:54 UTC
Description of problem:
A call to check_account_lock() (providing a slapi_entry) goes on to check
password expiry etc. with a call to new_passwdPolicy() passing in the DN of the
entry. new_passwdPolicy() then searches the db for the entry (that we already
have). This occurs in the bind code path so any optimization here would be good.
 There should be a way to pass in the entry to avoid the search.

new_passwdPolicy() seems to get called a lot in the password management code,
and there look to be other places that might be able to optimize out the search.

new_passwdPolicy() also has this comment
/*  If we're doing an add, COS does not apply yet so we check
                        parents for the pwdpolicysubentry.  We look only for virtual
                        attributes, because real ones are for single-target
policy. */

I'm not sure why this would be true - if an entry could be passed in in from the
add code this shouldn't be an issue I think, and the whole policy searching
algorithm could be ripped out and rely on COS for adds too (might be an issue
with regards to whether the add op has succeeded yet or something).

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. Write code to call check_account_lock()
Actual results:

Slower binds

Expected results:

Faster binds

Additional info:

Comment 1 Rich Megginson 2007-02-19 23:50:20 UTC

*** This bug has been marked as a duplicate of 184130 ***

Comment 2 Chandrasekar Kannan 2008-08-11 23:50:10 UTC
Bug already CLOSED. setting screened+ flag

Note You need to log in before you can comment on or make changes to this bug.