Why is Spring Security working in Tomcat but not when deployed to Weblogic?

前端 未结 4 953
野性不改
野性不改 2021-01-03 00:03

I\'m not really a Java developer, but a project for a client has required me to be, so maybe I\'m missing something glaringly obvious.

I\'m using SpringBoot and ever

4条回答
  •  我在风中等你
    2021-01-03 00:43

    It sounds as though you are running into SEC-2465. In short, there is a bug in WebLogic related to adding Filter instances. From the above JIRA:

    Oracle acknowledged it as a bug: 17382048, fixed with patch 16769849. It is reported as being fixed in WLS 12.1.3

    The client should update their WebLogic server to get a fix. Alternatively, you can create your own version of AbstractSecurityWebApplicationInitializer that registers springSecurityFilterChain with the class method:

    servletContext.addFilter(String filterName, java.lang.Class filterClass)
    

    Your subclass of AbstractSecurityWebApplicationInitializer would then extend your custom class instead.

    Update

    Based on the updated information, I still contend the issue is related to the WebLogic bug mentioned above. When using SpringBootServletInitializer, the Filters are added with FilterRegistrationBean as an instance rather than a class.

    The easiest option is to update to WebLogic since everything should work as is.

    To workaround the issue, you can disable the registration of Spring Security and any other Filters. You can do this by creating a FilterRegistrationBean like the following:

    @Bean
    public FilterRegistrationBean springSecurityFilterChainRegistrationBean(@Qualifier("springSecurityFilterChain") Filter filter) {
        FilterRegistrationBean bean = new FilterRegistrationBean();
        bean.setFilter(filter);
        bean.setEnabled(false);
        return bean;
    }
    

    Then you need to ensure the Filter is registered using

    servletContext.addFilter(String filterName, java.lang.Class filterClass)
    

    Spring Security can be registered with the above mechanism by implementing WebApplicationInitializer. For example, you can create the following class:

    package demo;
    
    import java.util.EnumSet;
    
    import javax.servlet.FilterRegistration.Dynamic;
    import javax.servlet.*;
    
    import org.springframework.web.WebApplicationInitializer;
    import org.springframework.web.filter.DelegatingFilterProxy;
    
    public class SecurityInitializer implements WebApplicationInitializer {
    
        @Override
        public void onStartup(ServletContext context) throws ServletException {
            Dynamic registration =
                    context.addFilter("springSecurityFilterChain", DelegatingFilterProxy.class);
            EnumSet dispatcherTypes =
                    EnumSet.of(DispatcherType.REQUEST, DispatcherType.ERROR, DispatcherType.ASYNC);
            registration.addMappingForUrlPatterns(dispatcherTypes, true, "/*");
        }
    }
    

    DelegatingFilterProxy will look up a bean of the name "springSecurityFilterChain" and delegate to it every time doFilter is invoked.

提交回复
热议问题