Spring Security：Authentiation提供商和UserDetailsService无法按预期工作

Question

关于Spring Security性，我有两个问题。我在网上做了一系列研究，但答案要么肤浅，要么太复杂，对我的问题没有多大帮助。我试图在应用Java配置策略的应用程序中使用Spring Security性（完全没有xml）。

第一种情况是，我有一个扩展WebSecurityConfigureAdapter的SecurityConfiguration类。在这里，我有了我的自动连线登录服务（它实现了UserDetailsService），并且我已经将AuthenticationManagerBuilder的UserDetailsService定义为我的登录服务。

当我尝试使用我的表单登录时，LoginService成功地获得了用户（根据提供的用户名和密码），但不知何故身份验证失败，我在浏览器中收到来自Tomcat的403-拒绝访问消息。

第二种情况作为修复前一个问题的尝试，我创建了一个自定义AuthenticationProvider，并将其注入到我的SecurityConfiguration中。但是，当我尝试登录时，authenticate（）方法甚至不起作用。

有人能帮我吗？先谢谢你

SecurityConfiguration类

@Configuration
@EnableWebSecurity
public class SecurityConfiguration extends WebSecurityConfigurerAdapter{

private final String ADMIN_ROLE = "ADMIN";
private final String EMPLOYEE_ROLE = "EMPLOYEE";

@Autowired
private LoginService loginService;

@Autowired
public void configureGlobal ( AuthenticationManagerBuilder auth) throws Exception {

    auth.userDetailsService(loginService);
}

@Override
public void configure( WebSecurity web ) throws Exception {

    web.ignoring().antMatchers("/resources/**");
}

@Override
public void configure( HttpSecurity http ) throws Exception {

    http

        .authorizeRequests()
            .antMatchers("/login**", "/doLogin**").permitAll()
            .antMatchers("/admin", "/admin/**").hasRole(ADMIN_ROLE)
            .anyRequest().authenticated()
            .and()
        .requiresChannel()
            .anyRequest().requiresSecure()
            .and()
        .formLogin()
            .loginPage( "/login" )
            .loginProcessingUrl( "/doLogin" )
            .defaultSuccessUrl( "/admin" )
            .failureUrl( "/login?err=1" )
            .usernameParameter( "username" )
            .passwordParameter( "password" )
            .and()

        // This is where the logout page and process is configured. The logout-url is the URL to send
        // the user to in order to logout, the logout-success-url is where they are taken if the logout
        // is successful, and the delete-cookies and invalidate-session make sure that we clean up after logout
        .logout()
            .logoutRequestMatcher( new AntPathRequestMatcher( "/logout" ) )
            .logoutSuccessUrl( "/login?out=1" )
            .deleteCookies( "JSESSIONID" )
            .invalidateHttpSession( true )
            .and()

        // The session management is used to ensure the user only has one session. This isn't
        // compulsory but can add some extra security to your application.
        .sessionManagement()
            .invalidSessionUrl( "/login" )
            .maximumSessions( 1 );
}

}

登录服务类

@Service("loginService")
public class LoginService implements UserDetailsService{

@Autowired
private HibernateUserDAO hibernateUserDAO;

@Override
public UserDetails loadUserByUsername(String username)
        throws UsernameNotFoundException {

    User user = new User();
    user.setUsername(username);

    List<User> result = hibernateUserDAO.get(user);

    user = result.get(0);
    return user;
}
}

AuthProvider类

@Component("authProvider")
public class AuthProvider implements AuthenticationProvider {


@Autowired
private LoginService loginService;


@Override
public Authentication authenticate(Authentication auth)
        throws AuthenticationException {

    String username = auth.getName();
    String password = auth.getCredentials().toString();
    System.out.println(username + " " + password);

    UserDetails user = loginService.loadUserByUsername(username);
    System.out.println(user);
    if(user != null){

        Authentication token = new UsernamePasswordAuthenticationToken(username, password, user.getAuthorities());

        return token;
    }
    return null;
}

@Override
public boolean supports(Class<?> arg0) {
    // TODO Auto-generated method stub
    return false;
}

}

OBS：这里粘贴的SecurityConfiguration没有注入AuthProvider，但是作为一个信息，configureGlobal方法应该是这样的

@Autowired
private AuthProvider authProvider;

@Autowired
public void configureGlobal ( AuthenticationManagerBuilder auth) throws Exception {

    auth.authenticationProvider(authProvider);
}

Answer 1

问题解决了！HttpSecurity的hasRole（）方法似乎会检查角色的格式是否为“role_”（例如“role_ADMIN”），并且我的授权权限列表仅返回角色名称（例如“ADMIN”）。就这样。