comment on

I'm not really sure what you asking for in the last sentence, but I did read your meditation about WIP delivery system. My taste is to leverage what already exists (in this case using an ldap bind call to authenticate users). Do you ever anticipate implementing a password policy that requires changes (e.g. once a quarter)? In my project I have to be able to support a password policy for accounts in the directory -- so I think my authentication method has to be a bind as the user. Our directory is public so I don't think allowing anonymous access to userPassword would be a good idea.

Here is a code sample of what we're a prototyping:

# anonymous bind to determine user DN
$msg = $ldap->bind();
$msg = $ldap->search ( 
                       base => $BASE,
                       filter => "(uid=$uid)"
                     );

die "no entries" if ! $msg->count;

my $entry = $msg->shift_entry;
my $dn = $entry->dn;

$msg = $ldap->bind( $dn, password => $secret );
[download]

In reply to Re: Re: Re: Re: RFC: Net::LDAP::Simple by kennethwlangley
in thread RFC: Net::LDAP::Simple by bronto

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks