Re: Unable to do named binds against NDS 8

[Gary F. <fl...@jm...>]

----- Original Message -----
From: "Michael Wille" <mw...@do...>
Once I added the full dn to the named bind request, the bind was successful!
I guess you have to have every element, which is unfortunate.  If we are
using the bind for authentication in web apps, we really only know by
default the cn, o=WBDONER, and c=US.  Does anyone know if there is any other
way to find this info or not use it in the bind?  For performance reasons,
doing a search before the authentication is not desireable, nor is asking
the user which office and department they are from.


You might want to do some benchmarks to see if searching is that
much of a factor.