{"id":20200706,"url":"https://github.com/yifanzheng/spring-security-jwt","last_synced_at":"2025-05-12T14:29:20.774Z","repository":{"id":39656117,"uuid":"151277945","full_name":"yifanzheng/spring-security-jwt","owner":"yifanzheng","description":"使用 Spring Boot + Spring Security + JWT 实现用户登录验证示列，包含权限管理和 Token 刷新功能、心跳机制。","archived":false,"fork":false,"pushed_at":"2022-10-10T04:11:47.000Z","size":1083,"stargazers_count":207,"open_issues_count":1,"forks_count":44,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-05-12T14:29:13.991Z","etag":null,"topics":["java","jpa","jwt","jwt-token","spring-security"],"latest_commit_sha":null,"homepage":"","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/yifanzheng.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2018-10-02T15:28:42.000Z","updated_at":"2025-05-08T17:42:11.000Z","dependencies_parsed_at":"2023-01-19T17:33:04.922Z","dependency_job_id":null,"html_url":"https://github.com/yifanzheng/spring-security-jwt","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/yifanzheng%2Fspring-security-jwt","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/yifanzheng%2Fspring-security-jwt/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/yifanzheng%2Fspring-security-jwt/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/yifanzheng%2Fspring-security-jwt/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/yifanzheng","download_url":"https://codeload.github.com/yifanzheng/spring-security-jwt/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":253754733,"owners_count":21958901,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["java","jpa","jwt","jwt-token","spring-security"],"created_at":"2024-11-14T04:45:18.074Z","updated_at":"2025-05-12T14:29:20.743Z","avatar_url":"https://github.com/yifanzheng.png","language":"Java","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Spring Security With JWT\n\n### 概述\n\nSpring Security 是 Spring 全家桶中一个功能强大且高度可定制的身份验证和访问控制框架。与所有 Spring 项目一样，我们可以轻松扩展 Spring Security 以满足自定义要求。 \n\n由于 Spring Security 功能十分强大，相比于其他技术来说很难上手，很多刚接触 Spring Security 的开发者很难通过文档或者视频就能将其进行运用到实际开发中。\n\n在公司实习的时候接触到的一个项目就使用了 Spring Security 这个强大的安全验证框架来完成用户的登录模块，并且也是自己负责的一个模块。当时自己对 Spring Security 基本不熟悉，可以说是第一次接触，查阅了很多关于这方面的资料，看得似懂非懂的，并且还在导师的指导下都花了将近一周的时间才勉强完成。\n\nSpring Security 对于初学者来说，的确很难上手。于是自己在工作之余对这部分知识进行了学习，并实现了一个简单的项目，主要使用了 Spring Boot 技术集成 Spring Security 和 Spring Data Jpa 技术。这个项目实现的比较简单，还有很多地方需要优化，希望有兴趣的朋友可以一起完善，期待你的 PR。\n\n### 项目调整记录\n\n- 增加 Swagger UI，方便查看项目接口。\n- 增加全局异常捕获功能。\n- 增加 JPA 审计功能，完善数据表审计信息。\n- 在 Controller 层中暴露用户登录接口(`/api/auth/login`)。\n- 增加 Token 刷新功能，提供前端和后端各自的方案。\n\n### Token 刷新并发处理方案\n\n- 后端利用 Redis 缓存：https://github.com/yifanzheng/spring-security-jwt/tree/refresh-token-redis\n\n- 前端利用请求拦截器：https://github.com/yifanzheng/spring-security-jwt/tree/refresh-token-frontend\n\n\n### 项目下载\n\n- git clone https://github.com/yifanzheng/spring-security-jwt.git 。\n\n- 配置好 Maven 仓库，使用 IntelliJ IDEA 工具打开项目。\n\n- 在 application.properties 配置文件中将数据库信息改成你自己的。\n\n### 权限控制\n\n本 Demo 权限控制采用 RBAC 思想。简单地说，一个用户拥有若干角色，用户与角色形成多对多关系。\n\n**模型**\n![权限模型](https://img-blog.csdnimg.cn/20200628230812139.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L29zY2hpbmFfNDE3OTA5MDU=,size_16,color_FFFFFF,t_70)\n\n**数据表设计**\n\n用户表与用户角色表是多对多的关系。因为这里比较简单，所以表设计上有点冗余。小伙伴们可以根据实际情况重新设计。\n![表设计](https://img-blog.csdnimg.cn/2020062823082793.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L29zY2hpbmFfNDE3OTA5MDU=,size_16,color_FFFFFF,t_70)\n\n**数据交互**\n\n用户登录 -\u003e 后端验证登录并返回 token -\u003e 前端携带 token 请求后端数据 -\u003e 后端返回数据。\n\n![token流程](https://user-images.githubusercontent.com/22571230/138224284-770c1891-1be4-4c7d-9b76-c6b821f4e0b2.png)\n\n\n### 项目核心类说明\n\n**WebCorsConfiguration**  \n\nWebCorsConfiguration 配置类，主要解决 HTTP 请求跨域问题。这里需要注意的是，如果没有将 `Authorization` 头字段暴露给客户端的话，客户端是无法获取到 Token 信息的。\n\n```java\n/**\n * WebCorsConfiguration 跨域配置\n *\n * @author star\n */\n@Configuration\npublic class WebCorsConfiguration implements WebMvcConfigurer {\n\n    /**\n     * 设置swagger为默认主页\n     */\n    @Override\n    public void addViewControllers(ViewControllerRegistry registry) {\n        registry.addViewController(\"/\").setViewName(\"redirect:/swagger-ui.html\");\n        registry.setOrder(Ordered.HIGHEST_PRECEDENCE);\n        WebMvcConfigurer.super.addViewControllers(registry);\n    }\n\n    @Bean\n    public CorsFilter corsFilter() {\n        UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();\n        CorsConfiguration config = new CorsConfiguration();\n        config.setAllowCredentials(true);\n        config.setAllowedOrigins(Collections.singletonList(\"*\"));\n        config.setAllowedMethods(Collections.singletonList(\"*\"));\n        config.setAllowedHeaders(Collections.singletonList(\"*\"));\n        // 暴露 header 中的其他属性给客户端应用程序\n        config.setExposedHeaders(Arrays.asList(\n                \"Authorization\", \"X-Total-Count\", \"Link\",\n                \"Access-Control-Allow-Origin\",\n                \"Access-Control-Allow-Credentials\"\n        ));\n        source.registerCorsConfiguration(\"/**\", config);\n        return new CorsFilter(source);\n    }\n\n}\n```\n\n**SecurityConfiguration**  \n\nSecurityConfiguration 配置类继承了 Spring Security 的 WebSecurityConfigurerAdapter 类。WebSecurityConfigurerAdapter 类提供了默认的安全配置，并允许其他类通过覆盖其方法来扩展它并自定义安全配置。\n\n这里配置了如下内容：\n\n- 忽略某些不需要验证的就能访问的资源路径；\n\n- 在 Spring Security 机制中配置需要验证后才能访问的资源路径、不需要验证就可以访问的资源路径以及指定某些资源只能被特定角色访问。\n\n- 配置请求权限认证异常时的处理类；\n\n- 将自定义的 `JwtAuthorizationFilter` 过滤器添加到 Spring Security 机制中。\n\n```java\n\n/**\n * Web 安全配置\n *\n * @author star\n **/\n@Configuration\n@EnableWebSecurity\n@EnableGlobalMethodSecurity(prePostEnabled = true)\n@Import(SecurityProblemSupport.class)\npublic class SecurityConfiguration extends WebSecurityConfigurerAdapter {\n\n    @Autowired\n    private CorsFilter corsFilter;\n\n    @Autowired\n    private SecurityProblemSupport securityProblemSupport;\n\n    /**\n     * 使用 Spring Security 推荐的加密方式进行登录密码的加密\n     */\n    @Bean\n    public BCryptPasswordEncoder bCryptPasswordEncoder(){\n        return new BCryptPasswordEncoder();\n    }\n\n    /**\n     * 此方法配置的资源路径不会进入 Spring Security 机制进行验证\n     */\n    @Override\n    public void configure(WebSecurity web) {\n        web.ignoring()\n                .antMatchers(HttpMethod.OPTIONS, \"/**\")\n                .antMatchers(\"/app/**/*.{js,html}\")\n                .antMatchers(\"/v2/api-docs/**\")\n                .antMatchers(\"/i18n/**\")\n                .antMatchers(\"/test/**\")\n                .antMatchers(\"/content/**\")\n                .antMatchers(\"/webjars/springfox-swagger-ui/**\")\n                .antMatchers(\"/swagger-resources/**\")\n                .antMatchers(\"/swagger-ui.html\");\n    }\n\n    /**\n     * 定义安全策略，设置 HTTP 访问规则\n     */\n    @Override\n    protected void configure(HttpSecurity http) throws Exception {\n        http\n                .addFilterBefore(corsFilter, UsernamePasswordAuthenticationFilter.class)\n                .exceptionHandling()\n                // 当用户无权访问资源时发送 401 响应\n                .authenticationEntryPoint(new HttpStatusEntryPoint(HttpStatus.UNAUTHORIZED))\n                // 当用户访问资源因权限不足时发送 403 响应\n                .accessDeniedHandler(securityProblemSupport)\n             .and()\n                // 禁用 CSRF\n                .csrf().disable()\n                .headers().frameOptions().disable()\n             .and()\n                .logout().logoutUrl(\"/auth/logout\").and()\n                .authorizeRequests()\n                 // 指定路径下的资源需要进行验证后才能访问\n                .antMatchers(\"/\").permitAll()\n                // 配置登录地址\n                .antMatchers(HttpMethod.POST, SecurityConstants.AUTH_LOGIN_URL).permitAll()\n                .antMatchers(HttpMethod.POST,\"/api/users/register\").permitAll()\n                // 其他请求需验证\n                .anyRequest().authenticated()\n             .and()\n                // 不需要 session（不创建会话）\n                .sessionManagement()\n                .sessionCreationPolicy(SessionCreationPolicy.STATELESS)\n             .and()\n               .apply(securityConfigurationAdapter());\n        super.configure(http);\n    }\n\n    private JwtConfigurer securityConfigurationAdapter() throws Exception{\n        return new JwtConfigurer(new JwtAuthorizationFilter(authenticationManager()));\n    }\n}\n```\n\n**JwtAuthorizationFilter**\n\nJwtAuthorizationFilter 用户请求授权过滤器，用于从用户请求中获取 token 信息，并对其进行验证，同时加载与 token 相关联的用户身份认证信息，并添加到 Spring Security 上下文中。\n\n```java\n/**\n * JwtAuthorizationFilter 用户请求授权过滤器\n *\n * \u003cp\u003e\n * 提供请求授权功能。用于处理所有 HTTP 请求，并检查是否存在带有正确 token 的 Authorization 标头。\n * 如果 token 有效，则过滤器会将身份验证数据添加到 Spring 的安全上下文中，并授权此次请求访问资源。\u003c/p\u003e\n *\n * @author star\n */\npublic class JwtAuthorizationFilter extends BasicAuthenticationFilter {\n\n    public JwtAuthorizationFilter(AuthenticationManager authenticationManager) {\n        super(authenticationManager);\n    }\n\n    @Override\n    protected void doFilterInternal(@NotNull HttpServletRequest request, @NotNull HttpServletResponse response, @NotNull FilterChain filterChain) throws ServletException, IOException {\n        // 从 HTTP 请求中获取 token\n        String token = this.getTokenFromHttpRequest(request);\n        // 验证 token 是否有效\n        if (StringUtils.hasText(token) \u0026\u0026 JwtUtils.validateToken(token)) {\n            // 获取认证信息\n            Authentication authentication = JwtUtils.getAuthentication(token);\n            // 将认证信息存入 Spring 安全上下文中\n            SecurityContextHolder.getContext().setAuthentication(authentication);\n        }\n        // 放行请求\n        filterChain.doFilter(request, response);\n\n    }\n\n    /**\n     * 从 HTTP 请求中获取 token\n     *\n     * @param request HTTP 请求\n     * @return 返回 token\n     */\n    private String getTokenFromHttpRequest(HttpServletRequest request) {\n        String authorization = request.getHeader(SecurityConstants.TOKEN_HEADER);\n        if (authorization == null || !authorization.startsWith(SecurityConstants.TOKEN_PREFIX)) {\n            return null;\n        }\n        // 去掉 token 前缀\n        return authorization.replace(SecurityConstants.TOKEN_PREFIX, \"\");\n    }\n\n}\n```\n\n**所有的用户请求**都会经过此过滤器，当请求进入过滤器后会经历如下步骤：\n\n- 首先，从请求中获取 token 信息，并检查 token 的有效性。\n\n- 如果 token 有效，则解析 token 获取用户名，然后使用用户名从数据库中获取用户角色信息，并在 Spring Security 的上下文中设置身份验证。\n\n- 如果 token 无效或请求不带 token 信息，则直接放行。\n\n特别说明，这里用户的角色信息，是从数据库中重新获取的。其实，这里也可以换成从 token 信息中解析出用户角色，这样可以避免直接访问数据库。\n\n但是，直接从数据库获取用户信息也是很有帮助的。例如，如果用户角色已更改，则可能要禁止使用此 token 进行访问。\n\n**JwtUtils**\n\nJwtUtils 工具类，在用户登录成功后，主要用于生成 token，并验证用户请求中发送的 token。\n\n```java\n/**\n * Jwt 工具类，用于生成、解析与验证 token\n *\n * @author star\n **/\npublic final class JwtUtils {\n\n    private static final Logger logger = LoggerFactory.getLogger(JwtUtils.class);\n\n    private static final byte[] secretKey = DatatypeConverter.parseBase64Binary(SecurityConstants.JWT_SECRET_KEY);\n\n    private JwtUtils() {\n        throw new IllegalStateException(\"Cannot create instance of static util class\");\n    }\n\n    /**\n     * 根据用户名和用户角色生成 token\n     *\n     * @param userName   用户名\n     * @param roles      用户角色\n     * @param isRemember 是否记住我\n     * @return 返回生成的 token\n     */\n    public static String generateToken(String userName, List\u003cString\u003e roles, boolean isRemember) {\n        byte[] jwtSecretKey = DatatypeConverter.parseBase64Binary(SecurityConstants.JWT_SECRET_KEY);\n        // 过期时间\n        long expiration = isRemember ? SecurityConstants.EXPIRATION_REMEMBER_TIME : SecurityConstants.EXPIRATION_TIME;\n        // 生成 token\n        String token = Jwts.builder()\n                // 生成签证信息\n                .setHeaderParam(\"typ\", SecurityConstants.TOKEN_TYPE)\n                .signWith(Keys.hmacShaKeyFor(jwtSecretKey), SignatureAlgorithm.HS256)\n                .setSubject(userName)\n                .claim(SecurityConstants.TOKEN_ROLE_CLAIM, roles)\n                .setIssuer(SecurityConstants.TOKEN_ISSUER)\n                .setIssuedAt(new Date())\n                .setAudience(SecurityConstants.TOKEN_AUDIENCE)\n                // 设置有效时间\n                .setExpiration(new Date(System.currentTimeMillis() + expiration * 1000))\n                .compact();\n        return token;\n    }\n\n    /**\n     * 验证 token 是否有效\n     *\n     * \u003cp\u003e\n     * 如果解析失败，说明 token 是无效的\n     *\n     * @param token token 信息\n     * @return 如果返回 true，说明 token 有效\n     */\n    public static boolean validateToken(String token) {\n        try {\n            getTokenBody(token);\n            return true;\n        } catch (ExpiredJwtException e) {\n            logger.warn(\"Request to parse expired JWT : {} failed : {}\", token, e.getMessage());\n        } catch (UnsupportedJwtException e) {\n            logger.warn(\"Request to parse unsupported JWT : {} failed : {}\", token, e.getMessage());\n        } catch (MalformedJwtException e) {\n            logger.warn(\"Request to parse invalid JWT : {} failed : {}\", token, e.getMessage());\n        } catch (IllegalArgumentException e) {\n            logger.warn(\"Request to parse empty or null JWT : {} failed : {}\", token, e.getMessage());\n        }\n        return false;\n    }\n\n    /**\n     * 根据 token 获取用户认证信息\n     *\n     * @param token token 信息\n     * @return 返回用户认证信息\n     */\n    public static Authentication getAuthentication(String token) {\n        Claims claims = getTokenBody(token);\n        // 获取用户角色字符串\n        List\u003cString\u003e roles = (List\u003cString\u003e)claims.get(SecurityConstants.TOKEN_ROLE_CLAIM);\n        List\u003cSimpleGrantedAuthority\u003e authorities =\n                Objects.isNull(roles) ? Collections.singletonList(new SimpleGrantedAuthority(UserRoleConstants.ROLE_USER)) :\n                        roles.stream()\n                                .map(SimpleGrantedAuthority::new)\n                                .collect(Collectors.toList());\n        // 获取用户名\n        String userName = claims.getSubject();\n\n        return new UsernamePasswordAuthenticationToken(userName, token, authorities);\n\n    }\n\n    private static Claims getTokenBody(String token) {\n        return Jwts.parser()\n                .setSigningKey(secretKey)\n                .parseClaimsJws(token)\n                .getBody();\n    }\n}\n```\n\n### 请求认证流程说明\n\n由于已将登录接口暴露在了 Controller 层，请求认证过程将变成，所有的请求会先经过 `JwtAuthorizationFilter` 过滤器，然后进入 Spring Security 机制中。\n\n### 测试 API\n\n**注册账号**\n![register](https://img-blog.csdnimg.cn/20200524195659308.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L29zY2hpbmFfNDE3OTA5MDU=,size_16,color_FFFFFF,t_70)\n**登录**\n![login](https://img-blog.csdnimg.cn/20200524195721904.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L29zY2hpbmFfNDE3OTA5MDU=,size_16,color_FFFFFF,t_70)\n**带上正确的 token 访问需要身份验证的资源**  \n![correctToken](https://img-blog.csdnimg.cn/20200524200233825.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L29zY2hpbmFfNDE3OTA5MDU=,size_16,color_FFFFFF,t_70)\n**带上不正确的 token 访问需要身份验证的资源**\n![incorrectToken](https://img-blog.csdnimg.cn/20200524200307326.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L29zY2hpbmFfNDE3OTA5MDU=,size_16,color_FFFFFF,t_70)\n\n**不带 token 访问需要身份验证的资源** \n![noToken](https://img-blog.csdnimg.cn/20200524200408739.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L29zY2hpbmFfNDE3OTA5MDU=,size_16,color_FFFFFF,t_70)\n\n\n### 参考文档\n\n- [https://www.callicoder.com/spring-boot-spring-security-jwt-mysql-react-app-part-2/\n](https://www.callicoder.com/spring-boot-spring-security-jwt-mysql-react-app-part-2/\n)\n- [https://segmentfault.com/a/1190000009231329](https://segmentfault.com/a/1190000009231329)\n\n- [https://www.springcloud.cc/spring-security.html](https://www.springcloud.cc/spring-security.html)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fyifanzheng%2Fspring-security-jwt","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fyifanzheng%2Fspring-security-jwt","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fyifanzheng%2Fspring-security-jwt/lists"}