Hi Thomas, I have seen this done in a project. As you probably know the Spring Security filter (actually its a whole filter chain) is configured in your root WebApplicationContext. You then configure a DelegatingFilterProxy in web.xml that finds the filter in the context and delegates all requests to it.
With Magnolia and Blossom you do it the same way, except instead of using DelegatingFilterProxy you use InstallationAwareDelegatingFilterProxy from Blossom. It will defer looking up the filter in the context until magnolia has installed/updated and your module have created the root WebApplicationContext. HTH, // Tobias On Mar 8, 2011, at 2:03 AM, Thomas Duffey wrote: > > Hello, > > Has anyone successfully integrated Spring Security with Magnolia? I am > working on this now to protect access to parts of our module but hoping to > leave existing Magnolia-based security as-is. Trying to figure out where to > configure the Spring Security filter chain. On another application that had > its own filter chain I initialized the Spring Security filter chain in > web.xml and then added the old filters as Spring Security custom filters but > am not sure exactly how to accomplish something like this with Magnoila. > > Tom > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
