Hi Claudia, If what you're trying to achieve is section of your website that requires visitors to login (rather than use Spring Security for logging into AdminCentral) then you should be able to configure the spring security filter in web.xml. The SS filter is actually a proxy that goes and finds the real filter in the Spring ApplicationContext. And, since the ApplicationContext is started by your module it won't be available when Magnolia is in install/update mode. To handle this case there's a class called InstallationAwareDelegatingFilterProxy which will delay connecting the filter until Magnolia has completed install/update.
It's also possible to add it to the filter chain if you want to centralize everything in your module and keep web.xml clean. Use info.magnolia.cms.filters.FilterDecorator for this. You shouldn't need to exclude anything on the filter chain unless you have added servlets in web.xml. // Tobias -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=e8fc4df7-15bd-49de-ae4f-27dc66ed6a45 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
