The following was tested with Resin 3.0.6.
$RESIN_HOME
refers to the root of your Resin
installation.
Resin provides several ways to support the container adapter. In the instructions below we have elected to maximise consistency with other container adapter configurations. This will allow Resin users to simply deploy the sample application and confirm correct configuration. Developers comfortable with Resin are naturally able to use its capabilities to package the JARs with the web application itself, and/or support single sign-on.
Copy the following files into
$RESIN_HOME/lib
:
aopalliance.jar
commons-logging.jar
spring.jar
acegi-security-resin-XX.jar
commons-codec.jar
burlap.jar
hessian.jar
Unlike the container-wide acegisecurity.xml
files used by other container adapters, each Resin web application
will contain its own
WEB-INF/resin-acegisecurity.xml
file. Each web
application will also contain a resin-web.xml
file
which Resin uses to start the container adapter:
<web-app> <authenticator> <type>org.springframework.security.adapters.resin.ResinAcegiAuthenticator</type> <init> <app-context-location>WEB-INF/resin-acegisecurity.xml</app-context-location> <key>my_password</key> </init> </authenticator> </web-app>
With the basic configuration provided above, none of the JAR
files listed (or acegi-security-XX.jar
) should be
in your application's WEB-INF/lib
. The realm name
indicated in your web.xml
does not matter with
Resin, as the relevant authentication class is indicated by the
<authenticator>
setting