Hi Randy,
I don't recall changes to beta2 that would cause something like
this. You can try a recent "nightly" to see if the problem is
still present. It may be found at:
<http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3/>
If still present, please supply a simple web application that
demonstrates the problem so we can diagnose the cause.
Thanks,
Larry
> -----Original Message-----
> From: Randy Layman [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 19, 2001 11:57 AM
> To: [EMAIL PROTECTED]
> Subject: TC3.3-b2 Upgrade Issue
>
>
>
> We tried upgrading to TC3.3-b2 from TC 3.3-b1 today and
> had a very
> strange problem, which forced us to revert back to b1.
>
> Unsecured pages worked just fine, but when accessing the secured
> pages (secured using form-based login), we were unable to get
> our custom
> authenticator to work. It seems like our authenticator was
> never being
> called and was never instantiated (adding log and System.out.println
> statements to the constructor and getCredentials method lead to this
> assumption).
>
> In the apps-APP.xml file we have the RequestInterceptor
> tag with our
> class in the class name attribute and the class itself
> extends RealmBase.
>
> Our platform is RedHat 7.1 using Sun's JDK1.3.1.
>
> Any thoughts?
>
> Randy
>
>
