Hi All,
Time for a mea culpa. In my original message, I said that this used to work
in 6.0.20. That's wasn't correct. The 6.0.20 version we were using was
patched to fix this very issue, but we had not applied that patch to the
6.0.29 build. When we patched the 6.0.29 code, all works as expected.
2011/2/4 Christopher Schultz :
> "
> Various JNDI realm improvements for Active Directory. These include the
> ability to specify a default role, optional handling for nested roles
> and an option to ignore PartialResultExceptions (markt).
> "
>
> Unfortunately, there's no bug number listed and no
Chris - I've already been through all the changes in JNDIRealm between the
two versions and nothing jumped out at me. Since I don't have much else to
go on, I'll give it another shot. The JNDI logging is probably worthwhile.
I'll have to investigate how to enable that.
André - I appreciate that fe
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon,
On 2/3/2011 5:36 PM, Brandon DuRette wrote:
One of our customers had configured JNDIRealm to authenticate against Active
Directory using the userPattern="DOMAIN/{0}". This was working great with
Tomcat 6.0.20 (wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon,
On 2/3/2011 5:36 PM, Brandon DuRette wrote:
> One of our customers had configured JNDIRealm to authenticate against Active
> Directory using the userPattern="DOMAIN/{0}". This was working great with
> Tomcat 6.0.20 (with my patch for 42579 ap
Hello,
One of our customers had configured JNDIRealm to authenticate against Active
Directory using the userPattern="DOMAIN/{0}". This was working great with
Tomcat 6.0.20 (with my patch for 42579 applied (IIRC, the first time it was
applied in the trunk it was misapplied)). However, when we upgra
