You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@shiro.apache.org by PeterLee <sa...@gmail.com> on 2015/05/01 05:33:17 UTC

Re: Shiro 1.2.1 and Servlet 3.x Async requests

As posted at
http://shiro-user.582556.n2.nabble.com/UnavailableSecurityManagerException-in-MDB-td7578445.html#a7578463,
I used the following parameters:

    <init-param>
         <param-name>staticSecurityManagerEnabled</param-name>
         <param-value>true</param-value>
     </init-param>

It can solve No SecurityManager issue.



--
View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-1-2-1-and-Servlet-3-x-Async-requests-tp7580526p7580534.html
Sent from the Shiro User mailing list archive at Nabble.com.

Re: Shiro 1.2.1 and Servlet 3.x Async requests

Posted by shirobytor <by...@gmail.com>.

So in the configuration for the DelegatingFilterProxy add the init-param.
like


    <filter>
        <filter-name>shiroFilter</filter-name>
       
<filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>
        <async-supported>true</async-supported>
        <init-param>
            <param-name>targetFilterLifecycle</param-name>
            <param-value>true</param-value>
        </init-param>
        <init-param>
            <param-name>staticSecurityManagerEnabled</param-name>
            <param-value>true</param-value>
        </init-param>
    </filter>

Thanks, will try

Mark



--
View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-1-2-1-and-Servlet-3-x-Async-requests-tp7580526p7580536.html
Sent from the Shiro User mailing list archive at Nabble.com.