I'm really confused by this - the Spring ShiroFilterFactoryBean uses the same PathMatchingFilterChainResolver that the IniShiroFilter does.
Still tracing... On Wed, May 12, 2010 at 4:07 PM, Les Hazlewood <[email protected]> wrote: > Hi Kalle, > > I wasn't aware of this, and I'm not sure what is wrong :/ I'll start > looking in to it right now. In the meantime, any test you could > provide would be helpful. I'll hopefully find out what is going on > though. > > Thanks for the heads-up! > > On Wed, May 12, 2010 at 3:29 PM, Kalle Korhonen > <[email protected]> wrote: >> Les - are you aware that some recent change has broken the path >> matching when you configure things via Spring and webapp context is >> used. Run the Spring sample - the default configuration uses "shiro" >> context and authentication just doesn't work because the resolver >> finds nothing configured for that url. However, if you change the >> Jetty configuration to publish to root context, everything works. This >> is not an issue with with the simple jsp "web" sample even if you use >> some other context than root. I can easily whip up an integration test >> for this but I bet you have a pretty good hunch of what might have >> broken it. >> >> Kalle >> >
