> > This makes sense to me, because this time we are performing a
> > 'search' operation and later a 'compare', and the server can be
> > stricter with permissions on compare (and that's my case)
> >
> that explains it, I had not heard of a server that had a difference
in
> that respect.
In my c
> What userid/password is used to retrieve the DN from the uid/cn?
Retrieving DN is done in the first phase, called 'search/bind' in
mod_authnz_ldap's documentation.
If AuthLDAPBindDN is not configured, then an anonymous bind is used
this time.
This makes sense to me, because this time we are p
> Hope commit over the next couple of days, just dispelled the two
bogus
> concerns I had. Can you suggest some doc on how your basic auth
> usernames have to relate to what is able to bind directly to the
LDAP
> server? I think the arrangement on your server w/ the UID being
able
> to bind as-
On Mon, Dec 7, 2009 at 6:34 AM, drot...@tiscali.it wrote:
> I would like your opinion for the patch I submitted in bug #48340.
> Several people asked in time for a similar feature, to avoid exposing
> password with AuthLDAPBindDN/Password when anonymous search is not
> feasible.
Hope commit over
I would like your opinion for the patch I submitted in bug #48340.
Several people asked in time for a similar feature, to avoid exposing
password with AuthLDAPBindDN/Password when anonymous search is not
feasible.
Regards,
Domenico
We Love Megapixel ! Fino al 40% di sconto per le stampe format
