We are using the delivered JNDIRealm class for LDAP authN in Tomcat
7.0.29 but we're running into some problems when the back end LDAP is a
little slow (another issue being addressed separately) and having
threads stack up and timeout. A thread dump shows we end up with a lot
of blocked threads,
On Mon, 2012-07-30 at 14:36 -0600, Mark Thomas wrote:
> On 30/07/2012 21:24, Kris Easter wrote:
> >
> ...
> >
> > If the user sits too long on the login page the session times out, even
> > if their credentials were authenticated successfully, and sends them
&g
I'm looking at the org.apache.catalina.authenticator.FormAuthenticator
class from the 7.0.29 src. This portion of the authenticate method
starting around line 301 is where I'm having a little problem:
if (log.isDebugEnabled()) {
log.debug("Authentication of '" + username + "' was successful")
> I think, if I replace the FormAuthenticator with an descendant, it'll
> solve the problem.
>
> To extend FormAuthenticator is simple, but how can I make Tomcat to use it?
I tested this out at one time but it was never placed in production. My
terse notes, which might be leaving something out,
We're using Form based JNDIRealm Authentication against an LDAP server
and it's all working fine except for one issue. When a user enters an
invalid username/password they get sent to the error page, but they also
get sent to the same error page if the LDAP server is down. Is there a
way to trap
