Hi Ted, Thanks very much for sharing your solution - hopefully this will help others in portlet environments as well!
Regards, Les On Fri, May 6, 2011 at 7:56 AM, tkofford <[email protected]> wrote: > Les, thanks a lot for the help and for the prompt reply! > > I did finally get it to work. I had to add the REQUEST & INCLUDE > <dispatcher> elements for the shiro filter mapping in my web.xml. Below is > the configuration that I have for shiro & struts: > > <filter> > <filter-name>shiro</filter-name> > > <filter-class>org.apache.shiro.web.servlet.IniShiroFilter</filter-class> > <init-param> > <param-name>configPath</param-name> > <param-value>classpath:shiro.ini</param-value> > </init-param> > </filter> > > <filter> > <filter-name>struts2</filter-name> > > <filter-class>org.apache.struts2.dispatcher.FilterDispatcher</filter-class> > </filter> > > <filter-mapping> > <filter-name>shiro</filter-name> > <url-pattern>/*</url-pattern> > <dispatcher>REQUEST</dispatcher> > <dispatcher>INCLUDE</dispatcher> > </filter-mapping> > > <filter-mapping> > <filter-name>struts2</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> > > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Shiro-enabled-Portlet-UnavailableSecurityManagerException-tp6334470p6337830.html > Sent from the Shiro User mailing list archive at Nabble.com.
