devbox
笔触狂放9
这个屌丝很懒，什么也没留下！
关注作者
热门标签
热门文章
当前位置:   article > 正文

spring security oauth2 常用授权方式配置详细教程（一）_tokenkeyaccess

作者：笔触狂放9 | 2024-02-15 11:53:22

赞

踩

tokenkeyaccess

1 spring security oauth2 简单配置说明（一）

配套源码：https://download.csdn.net/download/tiancxz/12902941

1.1 工程说明：

授权服务端口10101

资源服务端口10201

  1.     <modules>
  2.         <!-- 项目依赖-->
  3.         <module>spring-security-oauth2-dependencies</module>
  4.         <!-- 认证服务器-->
  5.         <module>spring-security-oauth2-server</module>
  6.         <!--资源服务器-->
  7.         <module>spring-security-oauth2-resource</module>
  8.     </modules>

2 spring-security-oauth2-server认证服务器配置

2.1 项目结构

OAuth2简单集成使用只需要继承配置两个适配器就行。

AuthorizationServerConfigurerAdapter授权服务配置适配器

WebSecurityConfigurerAdapter网站安全配置适配器

2.2 pom.xml引入

  1.         <dependency>
  2.             <groupId>org.springframework.cloud</groupId>
  3.             <artifactId>spring-cloud-starter-oauth2</artifactId>
  4.         </dependency>

2.3 AuthorizationServerConfiguration授权服务配置适配器

  1. @Configuration
  2. //标注为授权服务
  3. @EnableAuthorizationServer
  4. public class AuthorizationServerConfiguration extends AuthorizationServerConfigurerAdapter {
  5.  
  6.     //使用内存存储令牌（普通令牌）
  7.     @Bean
  8.     public TokenStore tokenStore() {
  9.         return new InMemoryTokenStore();
  10.     }
  11.  
  12.     //设置授权码模式的授权码如何存取，暂时采用内存方式
  13.     @Bean
  14.     public AuthorizationCodeServices authorizationCodeServices() {
  15.         return new InMemoryAuthorizationCodeServices();
  16.     }
  17.  
  18.     //配置服务端点信息
  19.     @Override
  20.     public void configure(AuthorizationServerEndpointsConfigurer endpoints) throws Exception {
  21.         endpoints
  22.                 .authorizationCodeServices(authorizationCodeServices())//授权码服务
  23.                 .tokenStore(tokenStore())//令牌管理服务
  24.                 .allowedTokenEndpointRequestMethods(HttpMethod.POST);
  25.     }
  26.  
  27.  
  28.     //客户端详情服务
  29.     @Override
  30.     public void configure(ClientDetailsServiceConfigurer clients) throws Exception {
  31.         clients.inMemory()// 使用in-memory存储
  32.                 .withClient("client")// client_id
  33.                 .secret(new BCryptPasswordEncoder().encode("secret"))//客户端密钥
  34.                 .authorizedGrantTypes("authorization_code", "password","client_credentials","implicit","refresh_token")// 该client允许的授权类型authorization_code,password,refresh_token,implicit,client_credentials
  35.                 .scopes("all")// 允许的授权范围
  36.                 .autoApprove(true)//false跳转到授权页面
  37.                 //加上验证回调地址
  38.                 .redirectUris("http://www.baidu.com")
  39.         ;
  40.     }
  41.  
  42.     //设置认证令牌放行
  43.     @Override
  44.     public void configure(AuthorizationServerSecurityConfigurer security){
  45.         security
  46.                 .tokenKeyAccess("permitAll()")                    //oauth/token_key是公开
  47.                 .checkTokenAccess("permitAll()")                  //oauth/check_token公开
  48.                 .allowFormAuthenticationForClients()				//表单认证（申请令牌）
  49.         ;
  50.     }
  51.  
  52. }

2.4 WebSecurityConfiguration Security网站安配置全适配器

  1. @Configuration
  2. @EnableWebSecurity
  3. @EnableGlobalMethodSecurity(prePostEnabled = true, securedEnabled = true, jsr250Enabled = true)
  4. public class WebSecurityConfiguration extends WebSecurityConfigurerAdapter {
  5.  
  6.     //密码编码器
  7.     @Bean
  8.     public PasswordEncoder passwordEncoder() {
  9.         return new BCryptPasswordEncoder();
  10.     }
  11.  
  12.     //认证服务器 配置用户认证
  13.     @Override
  14.     protected void configure(AuthenticationManagerBuilder auth) throws Exception {
  15.         auth.inMemoryAuthentication()
  16.                 //注意roles authorities 在后面的才会生效。
  17.                 //.roles("r1","r2").authorities("r3","r4")  roles无效 authorities有效
  18.                 //两种选一种
  19.                 //一般我们简单系统只需根据authorities权限配置就行
  20.                 .withUser("admin").password(passwordEncoder().encode("123456")).roles("r1","r2").authorities("r3","r4")
  21.                 .and()
  22.                 .withUser("user").password(passwordEncoder().encode("123456")).authorities("r3","r4").roles("r1","r2")
  23.         ;
  24.     }
  25.  
  26.     //安全拦截机制（最重要）
  27.     @Override
  28.     protected void configure(HttpSecurity http) throws Exception {
  29.         http.csrf().disable()
  30.                 .authorizeRequests()
  31.                 .antMatchers("/login*").permitAll()
  32.                 .anyRequest().authenticated()
  33.                 .and()
  34.                 .formLogin()
  35.                 .and()
  36.                 .csrf().disable() //打开的csrf保护
  37. //                .sessionManagement().sessionCreationPolicy(SessionCreationPolicy.STATELESS)//禁用session 默认授权页面将失效
  38.         ;
  39.         ;
  40.     }
  41.  
  42. }

3 spring-security-oauth2-resource 资源服务器配置

3.1 pom.xml引入

  1.         <!-- Spring Security -->
  2.         <dependency>
  3.             <groupId>org.springframework.cloud</groupId>
  4.             <artifactId>spring-cloud-starter-oauth2</artifactId>
  5.         </dependency>

3.2 ResourceServerConfiguration 资源服务适配器配置

  1. @Configuration
  2. @EnableResourceServer
  3. //方法拦截器
  4. @EnableGlobalMethodSecurity(prePostEnabled = true, securedEnabled = true, jsr250Enabled = true)
  5. public class ResourceServerConfiguration extends ResourceServerConfigurerAdapter {
  6.     @Override
  7.     public void configure(HttpSecurity http) throws Exception {
  8.         http.authorizeRequests()
  9.                 // 此处r1 r2 使用角色 r3 r4 使用权限
  10.                 // 验证WebSecurityConfiguration roles authorities 在后面的才会生效。
  11.                 // roles("r1","r2").authorities("r3","r4")  roles无效 authorities有效
  12.                 .antMatchers("/r1").hasAnyRole("r1")
  13.                 .antMatchers("/r2").hasAnyRole("r2")
  14.                 .antMatchers("/r3").hasAnyAuthority("r3")
  15.                 .antMatchers("/r4").hasAnyAuthority("r4")
  16.                 .antMatchers("/**").permitAll()
  17.                 ;
  18.     }
  19.  
  20.     //资源服务令牌解析服务 配置远程ResourceServerTokenServices后，可不用设置yml远程security.oauth2配置
  21.     @Bean
  22.     public ResourceServerTokenServices tokenService() {
  23.         //使用远程服务请求授权服务器校验token,必须指定校验token 的url、client_id，client_secret
  24.         RemoteTokenServices service=new RemoteTokenServices();
  25.         service.setCheckTokenEndpointUrl("http://localhost:10101/oauth/check_token");
  26.         service.setClientId("client");
  27.         service.setClientSecret("secret");
  28.         return service;
  29.     }
  30. }

3.3 application.yml配置认证服务器地址、id、密钥

  1. security:
  2.   oauth2:
  3.     client:
  4.       client-id: client
  5.       client-secret: secret
  6.       access-token-uri: http://localhost:10101/oauth/token
  7.       user-authorization-uri: http://localhost:10101/oauth/authorize
  8.     resource:
  9.       token-info-uri: http://localhost:10101/oauth/check_token

 

4 authorization_code授权码模式

4.1 启动测试

 

4.2 访问获取授权码

打开浏览器，输入地址：

http://localhost:10101/oauth/authorize?client_id=client&response_type=code

第一次访问会跳转到登录页面，输入用户名密码admin 123456，获取授权码

4.3 通过授权码向服务器申请令牌

http://client:secret@localhost:10101/oauth/token

也可以将client:secret@放置在请求参数里面

 

 

4.4 测试令牌

通过POSTMAN测试发现admin可以访问r3，r4。不能访问r1，r2

4.5 校验令牌

http://localhost:10101/oauth/check_token

5 password密码授权模式

对于我们内部网站或客户端，授权码模式过于复杂。可用密码模式做为自由传统网站。

在未对现有代码改动时，我们直接用PostMan调用会报错。

我们需要对现有代码进行改造。

5.1 WebSecurityConfiguration改造

  1.     //将认证管理器实例 注入到Spring
  2.     @Bean
  3.     public AuthenticationManager authenticationManagerBean() throws Exception {
  4.         return super.authenticationManagerBean();
  5.     }

5.2 AuthorizationServerConfiguration改造

  1.     //从spring获取认证管理器实例 支持密码授权模式
  2.     @Autowired
  3.     public AuthenticationManager authenticationManager;
  4.  
  5.     //配置服务端点信息 通过authenticationManager绑定指定认证管理器实例
  6.     @Override
  7.     public void configure(AuthorizationServerEndpointsConfigurer endpoints) throws Exception {
  8.         endpoints
  9.                 .authenticationManager(authenticationManager)//认证管理器 支持密码授权模式
  10.                 .authorizationCodeServices(authorizationCodeServices())//授权码服务
  11.                 .tokenStore(tokenStore())//令牌管理服务
  12.                 .allowedTokenEndpointRequestMethods(HttpMethod.POST);
  13.     }

5.3 测试密码授权模式

6 client_credentials客户端授权模式

不需要改动代码，直接上PostMan测试。合适微服务服务后台相互调用。

项目中单独使用安全度不高。需要配合网关gateway进行authorization_code、password授权模式对外部请求资源拦截。

 

7 implicit授权模式

已过时。只合适某些静态资源。无需额外配置。

http://localhost:10101/oauth/authorize?client_id=client&response_type=token

登陆后返回的地址直接加上了token

https://www.baidu.com/#access_token=29cb038d-2b05-4288-9d5d-ab4486a4ed2b&token_type=bearer&expires_in=3599&scope=all

 

 

8 刷新令牌

8.1 AuthorizationServerConfiguration修改支持令牌刷新

  1.     //令牌管理服务
  2.     public AuthorizationServerTokenServices tokenService() {
  3.         //刷新refresh_token模式支持
  4.         DefaultTokenServices tokenServices = new DefaultTokenServices();
  5.         //配置令牌
  6.         tokenServices.setTokenStore(tokenStore());
  7.         // access token有效期2个小时
  8.         tokenServices.setAccessTokenValiditySeconds(60*60*1);
  9.         // refresh token有效期30天
  10.         tokenServices.setRefreshTokenValiditySeconds(60*60*24*30);
  11.         // 支持使用refresh token刷新access token
  12.         tokenServices.setSupportRefreshToken(true);
  13.         // 允许重复使用refresh token
  14.         tokenServices.setReuseRefreshToken(false);
  15.         return tokenServices;
  16.     }
  17.  
  18.  
  19.     //配置服务端点信息
  20.     @Override
  21.     public void configure(AuthorizationServerEndpointsConfigurer endpoints) throws Exception {
  22.         endpoints
  23.                 .authorizationCodeServices(authorizationCodeServices())//授权码服务
  24.                 .authenticationManager(authenticationManager)//认证管理器 支持密码授权模式
  25. //                .tokenStore(tokenStore())//令牌 配置令牌管理服务后可以注释
  26.                 .tokenServices(tokenService())//令牌管理服务
  27.                 .allowedTokenEndpointRequestMethods(HttpMethod.POST)
  28.         ;
  29.     }

8.2 测试刷新令牌

 

9 自定义获取数据库用户权限实现

9.1 UserDetailsService实现

根据用户名获取用户的权限

  1. @Service
  2. public class UserDetailsServiceImpl implements UserDetailsService {
  3.  
  4.     @Autowired
  5.     private TbUserService tbUserService;
  6.  
  7.     @Autowired
  8.     private TbPermissionService tbPermissionService;
  9.  
  10.     @Override
  11.     public UserDetails loadUserByUsername(String userName) throws UsernameNotFoundException {
  12.  
  13.         TbUser tbUser = tbUserService.getByUserName(userName);
  14.         //框架存放权限的地方
  15.         List<GrantedAuthority> grantedAuthorities = Lists.newArrayList();
  16.         if (tbUser != null){
  17.             List<TbPermission> tbPermissions = tbPermissionService.selectByUserId(tbUser.getId());
  18.             tbPermissions.forEach(tbPermission -> {
  19.                 GrantedAuthority grantedAuthority = new SimpleGrantedAuthority(tbPermission.getEnname());
  20.                 grantedAuthorities.add(grantedAuthority);
  21.             });
  22.         }
  23.         //认证是交给框架完成的 这边直接返回框架User
  24.         return new User(tbUser.getUsername(),tbUser.getPassword(),grantedAuthorities);
  25.     }
  26. }

相关数据库表数据

9.2 WebSecurityConfiguration修改

WebSecurityConfiguration加载自定义UserDetailsService

  1.     //返回一个自定义数据库获取用户权限的实现
  2.     @Autowired
  3.     public  UserDetailsServiceImpl userDetailsService;
  4.  
  5.     //认证服务器 配置用户认证
  6.     @Override
  7.     protected void configure(AuthenticationManagerBuilder auth) throws Exception {
  8.           auth.userDetailsService(userDetailsService);
  9. //        auth.inMemoryAuthentication()
  10. //                //注意roles authorities 在后面的才会生效。
  11. //                //.roles("r1","r2").authorities("r3","r4")  roles无效 authorities有效
  12. //                //两种选一种
  13. //                //一般我们简单系统只需根据authorities权限配置就行
  14. //                .withUser("admin").password(passwordEncoder().encode("123456")).roles("r1","r2").authorities("r3","r4")
  15. //                .and()
  16. //                .withUser("user").password(passwordEncoder().encode("123456")).authorities("r3","r4").roles("r1","r2")
  17. //        ;
  18.     }

每次获取token时，都会进入自定义实现从数据库获取权限

http://client:secret@localhost:10101/oauth/token

10 @PreAuthorize开启注解

10.1 引入spring-boot-starter-aop或者aspectjweaver

项目中已经引入spring-boot-starter-web，不用再引入spring-boot-starter-aop或者aspectjweaver。只需修改yml。

10.2 修改yml

如果已经引入spring-boot-starter-web或spring-boot-starter-aop，需要配置aop.auto = true。aspectjweaver不需要修改。

  1. spring: 
  2.   aop: 
  3.     auto: true

10.3 ResourceServerConfiguration修改

添加@EnableGlobalMethodSecurity(prePostEnabled = true)，注释http安全里面权限验证。

  1. @Configuration
  2. @EnableResourceServer
  3. @EnableGlobalMethodSecurity(prePostEnabled = true, securedEnabled = true, jsr250Enabled = true)
  4. public class ResourceServerConfiguration extends ResourceServerConfigurerAdapter {
  5.  
  6.     @Override
  7.     public void configure(HttpSecurity http) throws Exception {
  8.         http
  9.                 .exceptionHandling()
  10.                 .and()
  11.                 .csrf().disable() //打开的csrf保护
  12.                 .sessionManagement().sessionCreationPolicy(SessionCreationPolicy.STATELESS)//禁用session
  13.                 .and()
  14.                 .authorizeRequests()
  15.                 // 以下为配置所需保护的资源路径及权限，需要与认证服务器配置的授权部分对应
  16.                 // 此处r1 r2 使用角色 r3 r4 使用权限
  17.                 // 验证WebSecurityConfiguration roles authorities 在后面的才会生效。
  18.                 // roles("r1","r2").authorities("r3","r4")  roles无效 authorities有效
  19. //                .antMatchers("/r1").hasAnyRole("r1")
  20. //                .antMatchers("/r2").hasAnyRole("r2")
  21. //                .antMatchers("/r3").hasAnyAuthority("r3")
  22. //                .antMatchers("/r4").hasAnyAuthority("r4")
  23.                 .antMatchers("/**").permitAll()
  24.                 ;
  25.     }

10.4 TbContentController修改

在具体方法添加@PreAuthorize("hasAnyAuthority('r5')")注解

10.5 测试

r4可以访问，r5不能访问

 

11 JWT令牌配置

11.1 pom.xml修改

资源服务器必须引入

  1.         <dependency>
  2.             <groupId>org.springframework.boot</groupId>
  3.             <artifactId>spring-boot-starter-aop</artifactId>
  4.         </dependency>

11.2 添加tokenConfig

认证服务器和资源服务器都需要

  1. @Configuration
  2. public class TokenConfig {
  3.  
  4.     //密钥
  5.     private String SIGNING_KEY = "hlcloud";
  6.  
  7.     @Bean
  8.     public TokenStore tokenStore() {
  9.         //JWT令牌存储方案
  10.         return new JwtTokenStore(accessTokenConverter());
  11.     }
  12.  
  13.     @Bean
  14.     public JwtAccessTokenConverter accessTokenConverter() {
  15.         JwtAccessTokenConverter converter = new JwtAccessTokenConverter();
  16.         converter.setSigningKey(SIGNING_KEY); //对称秘钥，资源服务器使用该秘钥来验证
  17.         return converter;
  18.     }
  19.  
  20.    /* @Bean
  21.     public TokenStore tokenStore() {
  22.         //使用内存存储令牌（普通令牌）
  23.         return new InMemoryTokenStore();
  24.     }*/
  25. }

11.3 认证服务器修改

AuthorizationServerConfiguration
  1. //    //使用内存存储令牌（普通令牌）
  2. //    @Bean
  3. //    public TokenStore tokenStore() {
  4. //        return new InMemoryTokenStore();
  5. //    }
  6.  
  7.     //使用JWT令牌存储方案
  8.     @Autowired
  9.     public TokenStore tokenStore;
  10.  
  11.     //使用jwt令牌转换加密
  12.     @Autowired
  13.     private JwtAccessTokenConverter accessTokenConverter;
  14.  
  15.     //令牌管理服务
  16.     public AuthorizationServerTokenServices tokenService() {
  17.         //刷新refresh_token模式支持
  18.         DefaultTokenServices tokenServices = new DefaultTokenServices();
  19.         //配置令牌
  20.         tokenServices.setTokenStore(tokenStore);
  21.         // access token有效期24个小时
  22.         tokenServices.setAccessTokenValiditySeconds(60*60*24);
  23.         // refresh token有效期3天
  24.         tokenServices.setRefreshTokenValiditySeconds(60*60*24*3);
  25.         // 支持使用refresh token刷新access token
  26.         tokenServices.setSupportRefreshToken(true);
  27.         // 允许重复使用refresh token
  28.         tokenServices.setReuseRefreshToken(false);
  29.  
  30.         //令牌增强 jwt转换
  31.         TokenEnhancerChain tokenEnhancerChain = new TokenEnhancerChain();
  32.         tokenEnhancerChain.setTokenEnhancers(Arrays.asList(accessTokenConverter));
  33.         tokenServices.setTokenEnhancer(tokenEnhancerChain);
  34.  
  35.         return tokenServices;
  36.     }

11.4 资源服务器修改

ResourceServerConfiguration注释远程调用验证token，jwt本地解密验证。
  1. //    //资源服务令牌解析服务 配置远程ResourceServerTokenServices后，可不用设置yml远程auth配置
  2. //    @Bean
  3. //    public ResourceServerTokenServices tokenService() {
  4. //        //使用远程服务请求授权服务器校验token,必须指定校验token 的url、client_id，client_secret
  5. //        RemoteTokenServices service=new RemoteTokenServices();
  6. //        service.setCheckTokenEndpointUrl("http://localhost:10101/oauth/check_token");
  7. //        service.setClientId("client");
  8. //        service.setClientSecret("secret");
  9. //        return service;
  10. //    }

11.5 测试

此时看到返回的令牌已经变长

测试资源服务器

12 认证服务JDBC改造

12.1 授权码JDBC改造

  1. //    //设置授权码模式的授权码如何存取，暂时采用内存方式
  2. //    @Bean
  3. //    public AuthorizationCodeServices authorizationCodeServices() {
  4. //        return new InMemoryAuthorizationCodeServices();
  5. //    }
  6.  
  7.     //设置授权码模式的授权码如何存取，暂时采用内存方式
  8.     @Bean
  9.     public AuthorizationCodeServices authorizationCodeServices(DataSource dataSource) {
  10.         return new JdbcAuthorizationCodeServices(dataSource);
  11.     }
  12.  
  13.     @Autowired
  14.     public AuthorizationCodeServices authorizationCodeServices;

12.2 客户端详情JDBC改造

  1.     //将客户端信息存储到数据库
  2.     @Bean
  3.     public JdbcClientDetailsService jdbcClientDetailsService(DataSource dataSource) {
  4.         return new JdbcClientDetailsService(dataSource);
  5.     }
  6.  
  7.     @Autowired
  8.     private JdbcClientDetailsService jdbcClientDetailsService;
  9.  
  10.     //客户端详情服务
  11.     @Override
  12.     public void configure(ClientDetailsServiceConfigurer clients) throws Exception {
  13.         clients.withClientDetails(jdbcClientDetailsService);
  14. //        clients.inMemory()// 使用in-memory存储
  15. //                .withClient("client")// client_id
  16. //                .secret(new BCryptPasswordEncoder().encode("secret"))//客户端密钥
  17. //                .authorizedGrantTypes("authorization_code", "password","client_credentials","implicit","refresh_token")// 该client允许的授权类型authorization_code,password,refresh_token,implicit,client_credentials
  18. //                .scopes("all")// 允许的授权范围
  19. //                .autoApprove(true)//false跳转到授权页面
  20. //                //加上验证回调地址
  21. //                .redirectUris("http://www.baidu.com")
  22. //        ;
  23.     }

12.3 资源服务器ResourceServerConfiguration修改

如果不想使用使用resource_ids，可不用做这一步。添加了resid则需要在数据库里面修改响应字段。

  1.     @Override
  2.     public void configure(ResourceServerSecurityConfigurer resources) throws Exception {
  3.         resources.resourceId("res_id")
  4.                 .stateless(true);
  5.         ;
  6.         super.configure(resources);
  7.     }

12.4 相关表结构

oauth_client_details：存储客户端详情

oauth_code：存储授权码

  1. /*
  2.  Navicat Premium Data Transfer
  4.  Source Server         : 127.0.0.1-test
  5.  Source Server Type    : MySQL
  6.  Source Server Version : 50731
  7.  Source Host           : 127.0.0.1:3306
  8.  Source Schema         : oauth2
  10.  Target Server Type    : MySQL
  11.  Target Server Version : 50731
  12.  File Encoding         : 65001
  14.  Date: 30/09/2020 13:46:39
  15. */
  16.  
  17. SET NAMES utf8mb4;
  18. SET FOREIGN_KEY_CHECKS = 0;
  19.  
  20. -- ----------------------------
  21. -- Table structure for oauth_access_token
  22. -- ----------------------------
  23. DROP TABLE IF EXISTS `oauth_access_token`;
  24. CREATE TABLE `oauth_access_token`  (
  25.   `token_id` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  26.   `token` blob NULL,
  27.   `authentication_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  28.   `user_name` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  29.   `client_id` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  30.   `authentication` blob NULL,
  31.   `refresh_token` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  32.   PRIMARY KEY (`authentication_id`) USING BTREE
  33. ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
  34.  
  35. -- ----------------------------
  36. -- Records of oauth_access_token
  37. -- ----------------------------
  38.  
  39. -- ----------------------------
  40. -- Table structure for oauth_approvals
  41. -- ----------------------------
  42. DROP TABLE IF EXISTS `oauth_approvals`;
  43. CREATE TABLE `oauth_approvals`  (
  44.   `userId` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  45.   `clientId` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  46.   `scope` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  47.   `status` varchar(10) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  48.   `expiresAt` timestamp(0) NULL DEFAULT NULL,
  49.   `lastModifiedAt` timestamp(0) NULL DEFAULT NULL
  50. ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
  51.  
  52. -- ----------------------------
  53. -- Records of oauth_approvals
  54. -- ----------------------------
  55.  
  56. -- ----------------------------
  57. -- Table structure for oauth_client_details
  58. -- ----------------------------
  59. DROP TABLE IF EXISTS `oauth_client_details`;
  60. CREATE TABLE `oauth_client_details`  (
  61.   `client_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  62.   `resource_ids` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  63.   `client_secret` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  64.   `scope` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  65.   `authorized_grant_types` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  66.   `web_server_redirect_uri` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  67.   `authorities` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  68.   `access_token_validity` int(11) NULL DEFAULT NULL,
  69.   `refresh_token_validity` int(11) NULL DEFAULT NULL,
  70.   `additional_information` varchar(4096) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  71.   `autoapprove` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  72.   PRIMARY KEY (`client_id`) USING BTREE
  73. ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
  74.  
  75. -- ----------------------------
  76. -- Records of oauth_client_details
  77. -- ----------------------------
  78. INSERT INTO `oauth_client_details` VALUES ('client', 'res_id', '$2a$10$/Sm77HZ5AFy.ZhwnjoIxn.VC7TNrr9/RaXZeYVf7V8mqG9VLrF8jK', 'all', 'authorization_code,password,client_credentials,implicit,refresh_token', 'http://www.baidu.com', NULL, NULL, NULL, NULL, 'true');
  79.  
  80. -- ----------------------------
  81. -- Table structure for oauth_client_token
  82. -- ----------------------------
  83. DROP TABLE IF EXISTS `oauth_client_token`;
  84. CREATE TABLE `oauth_client_token`  (
  85.   `token_id` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  86.   `token` blob NULL,
  87.   `authentication_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  88.   `user_name` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  89.   `client_id` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  90.   PRIMARY KEY (`authentication_id`) USING BTREE
  91. ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
  92.  
  93. -- ----------------------------
  94. -- Records of oauth_client_token
  95. -- ----------------------------
  96.  
  97. -- ----------------------------
  98. -- Table structure for oauth_code
  99. -- ----------------------------
  100. DROP TABLE IF EXISTS `oauth_code`;
  101. CREATE TABLE `oauth_code`  (
  102.   `code` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  103.   `authentication` blob NULL
  104. ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
  105.  
  106.  
  107. -- ----------------------------
  108. -- Table structure for oauth_refresh_token
  109. -- ----------------------------
  110. DROP TABLE IF EXISTS `oauth_refresh_token`;
  111. CREATE TABLE `oauth_refresh_token`  (
  112.   `token_id` varchar(256) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  113.   `token` blob NULL,
  114.   `authentication` blob NULL
  115. ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
  116.  
  117. -- ----------------------------
  118. -- Records of oauth_refresh_token
  119. -- ----------------------------
  120.  
  121. -- ----------------------------
  122. -- Table structure for tb_permission
  123. -- ----------------------------
  124. DROP TABLE IF EXISTS `tb_permission`;
  125. CREATE TABLE `tb_permission`  (
  126.   `id` bigint(20) NOT NULL AUTO_INCREMENT,
  127.   `parent_id` bigint(20) NULL DEFAULT NULL COMMENT '父权限',
  128.   `name` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT '权限名称',
  129.   `enname` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT '权限英文名称',
  130.   `url` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT '授权路径',
  131.   `description` varchar(200) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '备注',
  132.   `created` datetime(0) NOT NULL,
  133.   `updated` datetime(0) NOT NULL,
  134.   PRIMARY KEY (`id`) USING BTREE
  135. ) ENGINE = InnoDB AUTO_INCREMENT = 49 CHARACTER SET = utf8 COLLATE = utf8_general_ci COMMENT = '权限表' ROW_FORMAT = Dynamic;
  136.  
  137. -- ----------------------------
  138. -- Records of tb_permission
  139. -- ----------------------------
  140. INSERT INTO `tb_permission` VALUES (37, 0, '系统管理', 'System', '/', NULL, '2019-04-04 23:22:54', '2019-04-04 23:22:56');
  141. INSERT INTO `tb_permission` VALUES (38, 37, '用户管理', 'SystemUser', '/users/', NULL, '2019-04-04 23:25:31', '2019-04-04 23:25:33');
  142. INSERT INTO `tb_permission` VALUES (39, 38, '查看用户', 'SystemUserView', '/users/view/**', NULL, '2019-04-04 15:30:30', '2019-04-04 15:30:43');
  143. INSERT INTO `tb_permission` VALUES (40, 38, '新增用户', 'SystemUserInsert', '/users/insert/**', NULL, '2019-04-04 15:30:31', '2019-04-04 15:30:44');
  144. INSERT INTO `tb_permission` VALUES (41, 38, '编辑用户', 'SystemUserUpdate', '/users/update/**', NULL, '2019-04-04 15:30:32', '2019-04-04 15:30:45');
  145. INSERT INTO `tb_permission` VALUES (42, 38, '删除用户', 'SystemUserDelete', '/users/delete/**', NULL, '2019-04-04 15:30:48', '2019-04-04 15:30:45');
  146. INSERT INTO `tb_permission` VALUES (44, 37, '内容管理', 'resource', '/', NULL, '2019-04-06 18:23:58', '2019-04-06 18:24:00');
  147. INSERT INTO `tb_permission` VALUES (45, 44, '查看内容', 'r1', '/r1', NULL, '2019-04-06 23:49:39', '2019-04-06 23:49:41');
  148. INSERT INTO `tb_permission` VALUES (46, 44, '新增内容', 'r2', '/r2', NULL, '2019-04-06 23:51:00', '2019-04-06 23:51:02');
  149. INSERT INTO `tb_permission` VALUES (47, 44, '编辑内容', 'r3', '/r3', NULL, '2019-04-06 23:51:04', '2019-04-06 23:51:06');
  150. INSERT INTO `tb_permission` VALUES (48, 44, '删除内容', 'r4', '/r4', NULL, '2019-04-06 23:51:08', '2019-04-06 23:51:10');
  151.  
  152. -- ----------------------------
  153. -- Table structure for tb_role
  154. -- ----------------------------
  155. DROP TABLE IF EXISTS `tb_role`;
  156. CREATE TABLE `tb_role`  (
  157.   `id` bigint(20) NOT NULL AUTO_INCREMENT,
  158.   `parent_id` bigint(20) NULL DEFAULT NULL COMMENT '父角色',
  159.   `name` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT '角色名称',
  160.   `enname` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT '角色英文名称',
  161.   `description` varchar(200) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '备注',
  162.   `created` datetime(0) NOT NULL,
  163.   `updated` datetime(0) NOT NULL,
  164.   PRIMARY KEY (`id`) USING BTREE
  165. ) ENGINE = InnoDB AUTO_INCREMENT = 38 CHARACTER SET = utf8 COLLATE = utf8_general_ci COMMENT = '角色表' ROW_FORMAT = Dynamic;
  166.  
  167. -- ----------------------------
  168. -- Records of tb_role
  169. -- ----------------------------
  170. INSERT INTO `tb_role` VALUES (37, 0, '超级管理员', 'admin', NULL, '2019-04-04 23:22:03', '2019-04-04 23:22:05');
  171.  
  172. -- ----------------------------
  173. -- Table structure for tb_role_permission
  174. -- ----------------------------
  175. DROP TABLE IF EXISTS `tb_role_permission`;
  176. CREATE TABLE `tb_role_permission`  (
  177.   `id` bigint(20) NOT NULL AUTO_INCREMENT,
  178.   `role_id` bigint(20) NOT NULL COMMENT '角色 ID',
  179.   `permission_id` bigint(20) NOT NULL COMMENT '权限 ID',
  180.   PRIMARY KEY (`id`) USING BTREE
  181. ) ENGINE = InnoDB AUTO_INCREMENT = 48 CHARACTER SET = utf8 COLLATE = utf8_general_ci COMMENT = '角色权限表' ROW_FORMAT = Dynamic;
  182.  
  183. -- ----------------------------
  184. -- Records of tb_role_permission
  185. -- ----------------------------
  186. INSERT INTO `tb_role_permission` VALUES (37, 37, 37);
  187. INSERT INTO `tb_role_permission` VALUES (38, 37, 38);
  188. INSERT INTO `tb_role_permission` VALUES (39, 37, 39);
  189. INSERT INTO `tb_role_permission` VALUES (40, 37, 40);
  190. INSERT INTO `tb_role_permission` VALUES (41, 37, 41);
  191. INSERT INTO `tb_role_permission` VALUES (42, 37, 42);
  192. INSERT INTO `tb_role_permission` VALUES (43, 37, 44);
  193. INSERT INTO `tb_role_permission` VALUES (44, 37, 45);
  194. INSERT INTO `tb_role_permission` VALUES (45, 37, 46);
  195. INSERT INTO `tb_role_permission` VALUES (46, 37, 47);
  196. INSERT INTO `tb_role_permission` VALUES (47, 37, 48);
  197.  
  198. -- ----------------------------
  199. -- Table structure for tb_user
  200. -- ----------------------------
  201. DROP TABLE IF EXISTS `tb_user`;
  202. CREATE TABLE `tb_user`  (
  203.   `id` bigint(20) NOT NULL AUTO_INCREMENT,
  204.   `username` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT '用户名',
  205.   `password` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT '密码，加密存储',
  206.   `phone` varchar(20) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '注册手机号',
  207.   `email` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '注册邮箱',
  208.   `created` datetime(0) NOT NULL,
  209.   `updated` datetime(0) NOT NULL,
  210.   PRIMARY KEY (`id`) USING BTREE,
  211.   UNIQUE INDEX `username`(`username`) USING BTREE,
  212.   UNIQUE INDEX `phone`(`phone`) USING BTREE,
  213.   UNIQUE INDEX `email`(`email`) USING BTREE
  214. ) ENGINE = InnoDB AUTO_INCREMENT = 38 CHARACTER SET = utf8 COLLATE = utf8_general_ci COMMENT = '用户表' ROW_FORMAT = Dynamic;
  215.  
  216. -- ----------------------------
  217. -- Records of tb_user
  218. -- ----------------------------
  219. INSERT INTO `tb_user` VALUES (37, 'admin', '$2a$10$9ZhDOBp.sRKat4l14ygu/.LscxrMUcDAfeVOEPiYwbcRkoB09gCmi', '15888888888', 'lee.lusifer@gmail.com', '2019-04-04 23:21:27', '2019-04-04 23:21:29');
  220.  
  221. -- ----------------------------
  222. -- Table structure for tb_user_role
  223. -- ----------------------------
  224. DROP TABLE IF EXISTS `tb_user_role`;
  225. CREATE TABLE `tb_user_role`  (
  226.   `id` bigint(20) NOT NULL AUTO_INCREMENT,
  227.   `user_id` bigint(20) NOT NULL COMMENT '用户 ID',
  228.   `role_id` bigint(20) NOT NULL COMMENT '角色 ID',
  229.   PRIMARY KEY (`id`) USING BTREE
  230. ) ENGINE = InnoDB AUTO_INCREMENT = 38 CHARACTER SET = utf8 COLLATE = utf8_general_ci COMMENT = '用户角色表' ROW_FORMAT = Dynamic;
  231.  
  232. -- ----------------------------
  233. -- Records of tb_user_role
  234. -- ----------------------------
  235. INSERT INTO `tb_user_role` VALUES (37, 37, 37);
  236.  
  237. SET FOREIGN_KEY_CHECKS = 1;

 

声明：本文内容由网友自发贡献，不代表【wpsshop博客】立场，版权归原作者所有，本站不承担相应法律责任。如您发现有侵权的内容，请联系我们。转载请注明出处：https://www.wpsshop.cn/w/笔触狂放9/article/detail/84364
推荐阅读
相关标签

Copyright © 2003-2013 www.wpsshop.cn 版权所有，并保留所有权利。

  

闽ICP备14008679号