I'm implementing Tiki with integration into a
preexisting LDAP directory. I ran into a nasty logic
error and a call to a nonexistant function while trying
to get things set up. Here's a patch for those parts of
the code.
I also made some internal changes to prevent username
discovery via anonymous binds since the LDAP server is
configured to block those... is there a good reason why
Tiki and/or Pear::Auth::LDAP decides to do this rather
than attempting to directly bind with the given
username and password?
Thanks,
David Parker
Novacoast, Inc.
dparker at novacoast dot com
Logged In: YES
user_id=807810
Thanks for the patch, David!
Logged In: YES
user_id=807810
Thanks for the bugfix. Checked into CVS.
As to your second answer, I don't have an answer. Perhaps
you can bring it up on the dev-list.
Logged In: YES
user_id=796785
Hi David,
I'm interested in your 'don't anouymous bind' patch.
Could you post that here please?
Don't anon bind when using LDAP
Logged In: YES
user_id=1257
Hi, sorry for the over 3 month delay in getting back to you.
I forgot to reply one day and lost your message in my inbox
:) Anyway, here's my old "don't anonymous bind" patch. I
haven't used it since my original post, but hopefully it
will be of some use.