WildFly上的Spring Security性：执行筛选器链时出错

Question

• Spring-boot-SAML-Integration on GitHub

通过将其作为Spring Boot应用程序运行（针对SDK内置的应用服务器运行），WebApp可以正常工作。

不幸的是，相同的AuthN进程在undertow/wildfly上根本不起作用。

根据日志，IdP实际上执行了AuthN进程：我的自定义userdetails实现的指令被正确执行。尽管有执行流程，但Spring并没有为当前用户设置和保存特权。

@Component
public class SAMLUserDetailsServiceImpl implements SAMLUserDetailsService {

    // Logger
    private static final Logger LOG = LoggerFactory.getLogger(SAMLUserDetailsServiceImpl.class);

    @Override
    public Object loadUserBySAML(SAMLCredential credential)
            throws UsernameNotFoundException, SSOUserAccountNotExistsException {
        String userID = credential.getNameID().getValue();
        if (userID.compareTo("[e-mail]") != 0) {     // We're simulating the data access.
            LOG.warn("SSO User Account not found into the system");
            throw new SSOUserAccountNotExistsException("SSO User Account not found into the system", userID);
        }
        LOG.info(userID + " is logged in");
        List<GrantedAuthority> authorities = new ArrayList<GrantedAuthority>();
        GrantedAuthority authority = new SimpleGrantedAuthority("ROLE_USER");
        authorities.add(authority);
        ExtUser userDetails = new ExtUser(userID, "password", true, true, true,
                true, authorities, "John", "Doe");
        return userDetails;
    }
}

在调试过程中，我发现问题出在FilterChainProxy类上。在运行时，ServletRequest的属性filter_appliced的值为空，因此Spring将清除SecurityContextHolder。

private final static String FILTER_APPLIED = FilterChainProxy.class.getName().concat(".APPLIED");

public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain)
        throws IOException, ServletException {
    boolean clearContext = request.getAttribute(FILTER_APPLIED) == null;
    if (clearContext) {
        try {
            request.setAttribute(FILTER_APPLIED, Boolean.TRUE);
            doFilterInternal(request, response, chain);
        } finally {
            SecurityContextHolder.clearContext();
            request.removeAttribute(FILTER_APPLIED);
        }
    } else {
        doFilterInternal(request, response, chain);
    }
}

在VMware vFabric tc服务器和Tomcat上，一切都运行得很好。你对解决这个问题有什么想法吗？

Answer 1

在调查这个问题时，我注意到身份验证请求中的cookie和引用存在一些混乱。

当前，如果将webapplication上下文更改为根上下文，则wildfly身份验证将起作用：

 <server name="default-server" default-host="webapp">
     <http-listener name="default" socket-binding="http"/>
     <host name="default-host" alias="localhost" default-web-module="sso.war"/>
 </server>

重新启动wildfly并清除cookie后，所有工作都将按预期进行