Since both Tomcact and Jetty are servlet containers, there should be zero difference on how Shiro integration works. Something else is going on in your setup that’s interfering with normal operations.
> On Jul 21, 2016, at 10:56 AM, [email protected] wrote: > > Ok, I finally made some progress. Seems that in order to get the Auth to > work under Tomcat, I had to switch to native Shiro Session Management by > adding the following properties to shiro.ini > > sessionManager = org.apache.shiro.web.session.mgt.DefaultWebSessionManager > securityManager.sessionManager = $sessionManager > > > I do not need these when running with Jetty. > > I would like to understand why the difference if anyone knows, and is anyone > else using Tomcat8 without any issues? > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Shiro-rediecting-back-to-Login-after-successful-Login-tp7581130p7581164.html > Sent from the Shiro User mailing list archive at Nabble.com. >
