Daniel Lopez wrote (2007-10-29 18:19):
I'd like to confirm that this strategy works (with a tiny detail I will
explain) and I have now an application that is able to authenticate through
the container in Resin and Tomcat.
The only detail I had to modify is that wherever it reads:
return
Hi Mattias,
Checking again, the method you mention did not work for me because it
is calling the PasswordDigest method that specifies the username and
password but not the realm, so it was using the default realm -
getting a different encription. I tried providing an empty realm but
that
Hi,
It took me a while because I was busy with other things but for the
benefit of future generations, I'd like to confirm that this strategy
works (with a tiny detail I will explain) and I have now an
application that is able to authenticate through the container in
Resin and Tomcat.
The
Thanks Mattias,
I had thought about the subclassing option, but I had to try to see if
there was some configuration option I had missed :). In any case, that
will work fine, I believe. I'll be out of town for a week but when I go
back I'll give it a go and let you know how it worked.
Thanks
Hi all,
Long story short: I started consulting in a company that is developing
a product using Tomcat. They want to be able to run the application in
different containers to make sure they are spec compliant and all, so
I suggested Resin as an alternative.
I've been able to configure the
You could probably implement your own authenticator, possibly just
subclassing the JdbcAuthenticator (see below), then use that
authenticator in resin-web.xml.
I myself wrote a patch for a Tomcat only webapp, that contains this
plus dummy implementations of Tomcat classes/interfaces like
