The tapestry-acegi module allows you to use the Acegi servlet filters as ServletRequestServicerFilters. So, you can just add a javax.servlet.Filter to the pipeline and it will automatically wrap it to adapt it to the proper interface. Since the "filterChainProxy" implements javax.servlet.Filter, I think that might just work. Of course, you can't really override a contribution. You'd actually have to change the tapestry-acegi hivemodule.xml file to get that to work. Why can't you just plug your own SSO filter into the existing pipeline by using a symbol override?
-----Original Message----- From: Gernot Stocker [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 12, 2006 7:42 AM To: Tapestry users Subject: Re: Tapestry + Acegi + Spring integration On Tuesday 11 July 2006 20:30, James Carman wrote: > Yeah, when I added tapestry-acegi support into our project at work, the > people were quite amazed at how easy it was to secure a page. Hi, I would like to use the tapestry-acegi project for ACEGI-security-checks in pages, having already implemented a SSO authentication javax.servlet.Filter / org.acegisecurity.ui.webapp.AuthenticationProcessingFilter for authentication. In order to get a cleaner tapestry integration I would like to move the glue configuration from web.xml into hivemodule.xml by using the existing Spring-internal FilterChainProxy configuration. Does something speak against overwriting the following hivemind configuration: <contribution configuration-id="tapestry.request.ServletRequestServicerPipeline"> <filter name="HttpSessionContextIntegrationFilter" before="*" object="service:HttpSessionContextIntegrationFilter"/> <filter name="AuthenticationProcessingFilter" after="HttpSessionContextIntegrationFilter" before="AnonymousProcessingFilter" object="service:${tapestry.acegi.authenticationProcessingFilter}"/> <filter name="AnonymousProcessingFilter" object="service:AnonymousProcessingFilter"/> </contribution> with: <contribution configuration-id="tapestry.request.ServletRequestServicerPipeline"> <filter name="SpringServletFilterConfiguration" before="*" object="spring:filterChainProxy"/> </contribution> Where the spring configuration looks something like this: <bean id="filterChainProxy" class="org.acegisecurity.util.FilterChainProxy"> <property name="filterInvocationDefinitionSource"> <value> CONVERT_URL_TO_LOWERCASE_BEFORE_COMPARISON PATTERN_TYPE_APACHE_ANT /**=httpSessionContextIntegrationFilter,authenticationProcessingFilter,anony mousProcessingFilter,exceptionTranslationFilter,filterInvocationInterceptor </value> </property> </bean> and do the @Secure Annotations still work after this change? Thanks, Gernot -- Gernot Stocker, Institute for Genomics and Bioinformatics(IGB) Petersgasse 14, 8010 Graz, Austria Tel.: ++43 316 873 5345 http://genome.tugraz.at --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
