Er, um, hemming and hawin. Can't I be lazy? Pouting in corner :)
Ok, I have my coffee now; much better.
Eric, first off, many many thanks for your assistance.
One last question, possibly.
It looks like I'm going to have to install some type of testbed in order to
debug httpd.exe 2.4.9 as compa
Still striking out. Any chance you can force it to use non-ssl ldap
and capture the traffic with wireshark to see how the queries differ?
I mistook the one long log line as the lookup, but it's just the configured URL.
On Wed, Apr 16, 2014 at 8:51 AM, Marshall Httpd
wrote:
> Ahh, sure thing.
>
>
On Tue, Apr 15, 2014 at 4:38 PM, Eric Covener wrote:
> Can you summarize how the logging differs in the two releases?
>
>
> Here are two candidates:
>
> *) mod_ldap: When looking up sub-groups, use an implicit objectClass=*
> instead of an explicit cn=* filter. [David Hawes ]
this one is n
Ahh, sure thing.
= httpd.exe 2.4.6 =
[Wed Apr 16 07:54:05.108585 2014] [ssl:info] [pid 1216:tid 972] [client
100.200.300.401:60878] AH01964: Connection to child 63 established (server
xxxdev.xxx.example.edu:443)
[Wed Apr 16 07:54:05.109585 2014] [ssl:debug] [pid 1216:tid 972]
ssl_engine_k
On Tue, Apr 15, 2014 at 5:36 PM, Marshall Httpd
wrote:
> Logging differences, sure thing...
I meant between 2.4.6 and 2.4.9 for the user that fails under 2.4.9.
--
Eric Covener
cove...@gmail.com
-
To unsubscribe, e-mail: user
Hey Eric,
Yeah, I _just_ ran across the "mod_ldap: When looking up sub-groups, use an
implicit objectClass=* instead of an explicit cn=* filter." for 2.4.7.
I just haven't wrapped my head around it just yet. Nor have I found the
bug fix entry for this in https://issues.apache.org
> Can you summa
Can you summarize how the logging differs in the two releases?
Here are two candidates:
*) mod_ldap: When looking up sub-groups, use an implicit objectClass=*
instead of an explicit cn=* filter. [David Hawes ]
*) mod_ldap: Change "LDAPReferrals off" to actually set the underlying LDAP
Hi,
Our httpd.exe was recently upgraded from 2.4.6 to 2.4.9. But, when that
happened, some of our users can no longer authenticate via LDAP. By
"some", I mean that we have 2 domains. Users from one domain are fine, but
users in the 2nd domain can no longer authenticate.
E.g. AD\steve can authe
