栏目分类:
子分类:
返回
名师互学网用户登录
快速导航关闭
当前搜索
当前分类
子分类
实用工具
热门搜索
名师互学网 > IT > 软件开发 > 后端开发 > Java

SpringSecurity前后端分离授权

Java 更新时间: 发布时间: IT归档 最新发布 模块sitemap 名妆网 法律咨询 聚返吧 英语巴士网 伯小乐 网商动力

SpringSecurity前后端分离授权

1. 授权

即不同的用户使用不同的功能。

1.1 授权基本流程

在SpringSecurity中,默认使用FilterSecurityInterceptor来进行权限校验。在FilterSecurityInterceptor中会从SecurityContextHolder获取其中的Authentication,然后获取其中的权限信息。判断当前用户是否包含访问资源的权限。

因此需要将权限信息存入Authentication,然后对资源设置相应的访问权限。

1.2 授权实现 1.2.1 设置资源访问权限
  • 开启配置:SecurityConfig类中添加如下注解:

    @EnableGlobalMethodSecurity(prePostEnabled = true)
    
  • 限权访问:判断当前用户是否拥有某权限。

    @RestController
    @RequestMapping("/hello")
    public class HelloController {
    
        @GetMapping
        @PreAuthorize("hasAnyAuthority('test')")
        public String hello(){
            return "hello";
        }
    
    }
    
1.2.2 封装权限信息
  • 修改登录服务,给定一个固定权限集合来模拟:

    @Service
    public class SysUserDetailServiceImpl implements UserDetailsService {
    
        @Autowired
        private SysUserMapper userMapper;
    
        @Autowired
        private PasswordEncoder passwordEncoder;
    
        @Override
        public UserDetails loadUserByUsername(String username) throws UsernameNotFoundException {
    
            // 查询用户信息
            QueryWrapper queryWrapper = new QueryWrapper<>();
            queryWrapper.eq("username",username);
            SysUser user = userMapper.selectOne(queryWrapper);
    
            if (Objects.isNull(user)){
                throw new RuntimeException("用户不存在");
            }
            // 固定权限信息设置
            List list = new LinkedList<>(Arrays.asList("test","admin"));
            return new LoginUser(user,list);
        }
    
    
    }
    
  • 修改LoginUser类,让SpringSecurity内部可以获取权限信息。

    @Data
    @AllArgsConstructor
    @ToString
    public class LoginUser implements UserDetails, Serializable {
    
        private SysUser user;
    
        // 自定义权限集合
        private List permissions;
    
        public LoginUser() {
        }
    
        public LoginUser(SysUser user, List permissions) {
            this.user = user;
            this.permissions = permissions;
        }
    
        // security要求权限类型(让自定义的转为当前类型,在security内部使用),不进行序列化
        @JSONField(serialize = false)
        private List authorities;
    
        // security内部方法,获取权限集合。
        @Override
        public Collection getAuthorities() {
    
            // 只在第一次进行类型转换
            if (authorities == null){
                authorities = permissions
                        .stream()
                        .map(SimpleGrantedAuthority::new)
                        .collect(Collectors.toList());
            }
    
            return authorities;
        }
    
        @Override
        public String getPassword() {
            return user.getPassword();
        }
    
        @Override
        public String getUsername() {
            return user.getUsername();
        }
    
        @Override
        public boolean isAccountNonExpired() {
            return true;
        }
    
        @Override
        public boolean isAccountNonLocked() {
            return true;
        }
    
        @Override
        public boolean isCredentialsNonExpired() {
            return true;
        }
    
        @Override
        public boolean isEnabled() {
            return true;
        }
    }
    
    
  • 修改JwtAuthenticationTokenFilter,再次访问时也将权限信息从redis中读出。

    @Component
    public class JwtAuthenticationTokenFilter extends OncePerRequestFilter {
    
        @Autowired
        private RedisCache redisCache;
    
        @Override
        protected void doFilterInternal(HttpServletRequest request, HttpServletResponse response, FilterChain filterChain) throws ServletException, IOException {
            // 获取token
            String token = request.getHeader("token");
            if (!StringUtils.hasText(token)) {
                //直接放行 让后面原生的 security 去拦截
                filterChain.doFilter(request, response);
                return;
            }
            // 解析token
            String userId;
            try {
                Claims claims = JwtUtil.parseJWT(token);
                userId = claims.getSubject();
            } catch (Exception e) {
                e.printStackTrace();
                throw new RuntimeException("token error");
            }
    
            // 从redis 获取用户信息
            String redisKey = "login:" + userId;
            LoginUser loginUser = redisCache.getCacheObject(redisKey);
            System.out.println(loginUser);
            if (Objects.isNull(loginUser)){
                throw new RuntimeException("用户未登录");
            }
    
            // 将用户信息存入SecurityContextHolder
            UsernamePasswordAuthenticationToken authenticationToken =
                    new UsernamePasswordAuthenticationToken(
                            loginUser,
                            null,
                            loginUser.getAuthorities());
            SecurityContextHolder.getContext().setAuthentication(authenticationToken);
    
            // 放行
            filterChain.doFilter(request, response);
        }
    
    }
    
    
1.2.3 从数据库获取权限信息
  • RBAC权限模型(Role- Based Access Control):基于角色的权限控制,目前使用最多也是相对来说通用易用的权限模型。
  • 表设计:可以通俗的理解为用户对应多个角色,一个角色对应多个权限,用户和角色是多对多的关系,权限和角色也是多对多的关系。

对应sql文件:


SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS = 0;

-- ----------------------------
-- Table structure for sys_menu
-- ----------------------------
DROP TABLE IF EXISTS `sys_menu`;
CREATE TABLE `sys_menu`  (
  `menu_id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT '菜单ID',
  `menu_name` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT '菜单名称',
  `status` char(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT '1' COMMENT '菜单状态(0正常 1停用)',
  `perms` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT NULL COMMENT '权限标识',
  `del_flag` int(11) NULL DEFAULT 0 COMMENT '是否删除(0为删除 1删除)',
  PRIMARY KEY (`menu_id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 2002 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_general_ci COMMENT = '菜单权限表' ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for sys_role
-- ----------------------------
DROP TABLE IF EXISTS `sys_role`;
CREATE TABLE `sys_role`  (
  `role_id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT '角色ID',
  `role_name` varchar(30) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT '角色名称',
  `role_key` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT NULL COMMENT '角色权限字符串',
  `status` char(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL DEFAULT '0' COMMENT '角色状态(0正常 1停用)',
  `del_flag` char(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT '0' COMMENT '删除标志(0存在 1删除)',
  PRIMARY KEY (`role_id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 100 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_general_ci COMMENT = '角色信息表' ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for sys_role_menu
-- ----------------------------
DROP TABLE IF EXISTS `sys_role_menu`;
CREATE TABLE `sys_role_menu`  (
  `role_id` bigint(20) NOT NULL COMMENT '角色ID',
  `menu_id` bigint(20) NOT NULL COMMENT '菜单ID',
  PRIMARY KEY (`role_id`, `menu_id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_general_ci COMMENT = '角色和菜单关联表' ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for sys_user
-- ----------------------------
DROP TABLE IF EXISTS `sys_user`;
CREATE TABLE `sys_user`  (
  `user_id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT '用户ID',
  `user_name` varchar(30) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT '' COMMENT '用户名',
  `password` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT '' COMMENT '密码',
  `status` char(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT '0' COMMENT '帐号状态(0正常 1停用)',
  `del_flag` char(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT '0' COMMENT '删除标志(0代表存在 2代表删除)',
  PRIMARY KEY (`user_id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 100 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_general_ci COMMENT = '用户信息表' ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for sys_user_role
-- ----------------------------
DROP TABLE IF EXISTS `sys_user_role`;
CREATE TABLE `sys_user_role`  (
  `user_id` bigint(20) NOT NULL COMMENT '用户ID',
  `role_id` bigint(20) NOT NULL COMMENT '角色ID',
  PRIMARY KEY (`user_id`, `role_id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_general_ci COMMENT = '用户和角色关联表' ROW_FORMAT = Dynamic;

SET FOREIGN_KEY_CHECKS = 1;

对应实体类:

@Data
@AllArgsConstructor
@NoArgsConstructor
@ToString
public class SysMenu implements Serializable {

    @TableId
    private Long menuId;

    private String menuName;

    private Character status;

    private String perms;

    private Integer delFlag;

}
@Data
@AllArgsConstructor
@NoArgsConstructor
@ToString
public class SysRole implements Serializable {

    @TableId
    private Long roleId;

    private String roleName;

    private String  roleKey;

    private Character status;

    private Character delFlag;
}

编写mapper实现权限菜单查询:

@Component
public interface SysMenuMapper extends BaseMapper {


    
    List getMenuByUserId(Long userId);

}

新建SysMenuMapper.xml实现sql方法






    

  • 修改登录方法
@Service
public class SysUserDetailServiceImpl implements UserDetailsService {

    @Autowired
    private SysUserMapper userMapper;

    @Autowired
    private SysMenuMapper menuMapper;



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

        // 查询用户信息
        QueryWrapper queryWrapper = new QueryWrapper<>();
        queryWrapper.eq("user_name",username);
        SysUser user = userMapper.selectOne(queryWrapper);

        if (Objects.isNull(user)){
            throw new RuntimeException("用户不存在");
        }
        List list = menuMapper.getMenuByUserId(user.getId());
        return new LoginUser(user,list);
    }

}
2. 全局异常处理

在SpringSecurity中使用ExceptionTranslationFilter来捕获认证或者授权异常。

  • 认证异常:会封装成AuthenticationException然后调用 AuthenticationEntryPoint对象的方法进行异常处理。即自定义类实现接口即可。
@Component
public class AuthenticationEntryPointImpl implements AuthenticationEntryPoint {

    
    @Override
    public void commence(HttpServletRequest request, HttpServletResponse response, AuthenticationException authException) throws IOException, ServletException {
        Result result = new Result(HttpStatus.UNAUTHORIZED.value(), "认证失败,请重新登录");
        String json = JSON.toJSONString(result);
        WebUtil.renderString(response,json);
    }

}
  • 授权异常会封装成AccessDeniedException然后调用AccessDeniedHandler对象的方法进行异常处理。即自定义类实现接口即可。
@Component
public class AccessDeniedHandlerImpl implements AccessDeniedHandler {

    
    @Override
    public void handle(HttpServletRequest request, HttpServletResponse response, AccessDeniedException accessDeniedException) throws IOException, ServletException {
        Result result = new Result(HttpStatus.FORBIDDEN.value(), "没有权限");
        String json = JSON.toJSONString(result);
        WebUtil.renderString(response,json);
    }
}
  • webUtil工具类
public class WebUtil {
    public static void renderString(HttpServletResponse response,String string){
        response.setStatus(200);
        response.setContentType("application/json");
        response.setCharacterEncoding("utf-8");
        try {
            response.getWriter().println(string);
        } catch (IOException e) {
            e.printStackTrace();
        }
    }
}
  • 将自定义异常配置到SpringSecurity:修改SecurityConfig
    @Autowired
    private JwtAuthenticationTokenFilter jwtAuthenticationTokenFilter;
    
    @Autowired
    private AuthenticationEntryPoint authenticationEntryPoint;

    @Autowired
    private AccessDeniedHandler accessDeniedHandler

    @Override
    protected void configure(HttpSecurity http) throws Exception {
        http
                //关闭csrf
                .csrf().disable()
                //不通过Session获取SecurityContext
                .sessionManagement().sessionCreationPolicy(SessionCreationPolicy.STATELESS)
                .and()
                .authorizeRequests()
                // 对于登录接口 允许匿名访问
                .antMatchers("/login").anonymous()
//                .antMatchers("/testCors").hasAuthority("system:dept:list222")
                // 除上面外的所有请求全部需要鉴权认证
                .anyRequest().authenticated();

        // 添加过滤器到某个过滤器前
        http.addFilterBefore(jwtAuthenticationTokenFilter, UsernamePasswordAuthenticationFilter.class);

//        配置异常处理器
        http.exceptionHandling()
//                配置认证失败处理器
                .authenticationEntryPoint(authenticationEntryPoint)
                .accessDeniedHandler(accessDeniedHandler);

	}
3. 跨域
  • 开启SpringBoot跨域:
@Configuration
public class CorsConfig implements WebMvcConfigurer {

    @Override
    public void addCorsMappings(CorsRegistry registry) {
        registry.addMapping("
    public boolean hasAuthority(String authority){
        // 获取当前用户权限
        Authentication authentication = SecurityContextHolder.getContext().getAuthentication();
        LoginUser user = (LoginUser) authentication.getPrincipal();
        List list = user.getPermissions();
        // 判断是否包含对应 authority 权限
        return list.contains(authority);
    }

}
  • 针对接口配置
@RestController
@RequestMapping("/hello")
public class HelloController {

    @GetMapping
    @PreAuthorize("@exRoot.hasAuthority('sys:hello:get')")
    public String hello(){
        return "hello";
    }

}
5. SCRF

SCRF是指跨站请求伪造,一种常见的web攻击。

SpringSecurity防止CSRF攻击是通过csrf_token。后端会生成一个csrf_token,前端发起请求时需要携带这个csrf_token,如果没有就不允许进行访问。

可以发现CSRF是依靠的cookie中所携带的认证信息;在前后端分离项目中认证信息是token,而token不是存储在cookie中,并且需要前端代码把token放在请求头中去携带提交,因此对CSRF攻击也不需要担心。

转载请注明:文章转载自 www.mshxw.com
本文地址:https://www.mshxw.com/it/956390.html
我们一直用心在做
关于我们 文章归档 网站地图 联系我们

版权所有 (c)2021-2022 MSHXW.COM

ICP备案号:晋ICP备2021003244-6号