I'm not sure at this point. It sounds like it's an issue with your Jersey setup which, unfortunately, I'm not overly familiar with. To troubleshoot, I would probably comment out the shiro filter and see what works. If it works with the Shiro filter commented out, but not with it enabled, then the next step would be to ensure that Shiro is actually redirecting to the correct location.
-Jared On Tue 18 Dec 2012 04:26:55 AM CST, AndyW wrote: > Hi Jared, > > Thanks a lot for your reply, it was very useful and helped me move onto my > next problem! Following your advice, I added this to my bootstrap: > > > > I then realised that my Jersey setup needed to be changed as well, so I > replaced this (in createJerseyServletModule): > > > > with this: > > > > So, now Shiro intercepts my service call, redirects to login.jsp, takes my > submitted login details, passes it to my custom realm, which authenticates > the user and then finally I'm redirected back to my original service call. > > A lot of progress there, but now when I reach the service call after being > authenticated, I get a 404 with Jetty claiming the service can't be found. > This continues until the globalSessionTimeout is reached, after which my > service calls then get redirected back to login.jsp. > > I'm missing something again! Can you point me in the right direction again > please? > > Thanks, > Andy. > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Problem-setting-up-form-based-authentication-with-Shiro-Guice-Jersey-Jetty-no-shiro-ini-tp7578065p7578069.html > Sent from the Shiro User mailing list archive at Nabble.com.
