Java 后端 / 系统课时
实现角色与权限授权
实现角色与权限授权
本课把“已登录”进一步收紧为“只有具备指定角色、权限或业务条件的用户才能调用接口”,并完成一套可运行、可验证的请求级授权配置。
学习目标
- 区分角色与权限,并建立可维护的授权粒度
- 使用
authorizeHttpRequests为不同接口配置访问规则 - 编写自定义
AuthorizationManager处理业务条件
先建立角色与权限模型
角色适合表达岗位或职责集合,例如 ADMIN、OPERATOR;权限适合表达最小操作能力,例如 report:read、user:delete。推荐让用户关联角色、角色再聚合权限,接口最终尽量检查权限,避免角色名称变化时大量修改代码。
hasRole("ADMIN") 默认检查 ROLE_ADMIN,而 hasAuthority("report:read") 按字符串精确匹配。请求授权由 AuthorizationFilter 把当前认证信息和请求交给 AuthorizationManager,拒绝时终止访问,允许时继续过滤器链。

配置请求级授权规则
下面的单文件示例依赖 spring-boot-starter-web 与 spring-boot-starter-security。规则按从具体到通用排列:公开接口放行,删除用户要求管理员角色,报表接口同时要求权限和租户请求头,其余 API 只要求登录,未声明路径默认拒绝。
package com.example.authorization;
import java.util.Map;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.http.HttpMethod;
import org.springframework.security.authorization.AuthorizationDecision;
import org.springframework.security.authorization.AuthorizationManager;
import org.springframework.security.config.Customizer;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configurers.AbstractHttpConfigurer;
import org.springframework.security.core.Authentication;
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.userdetails.UserDetails;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.provisioning.InMemoryUserDetailsManager;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.security.web.access.intercept.RequestAuthorizationContext;
import org.springframework.web.bind.annotation.DeleteMapping;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.PathVariable;
import org.springframework.web.bind.annotation.RestController;
@SpringBootApplication
public class AuthorizationDemoApplication {
public static void main(String[] args) {
SpringApplication.run(AuthorizationDemoApplication.class, args);
}
}
@Configuration
class SecurityConfig {
@Bean
SecurityFilterChain securityFilterChain(
HttpSecurity http,
AuthorizationManager<RequestAuthorizationContext> tenantReportAccess)
throws Exception {
http
.csrf(AbstractHttpConfigurer::disable)
.authorizeHttpRequests(authorize -> authorize
.requestMatchers("/public/**").permitAll()
.requestMatchers(HttpMethod.DELETE, "/api/users/**").hasRole("ADMIN")
.requestMatchers("/api/reports/**").access(tenantReportAccess)
.requestMatchers("/api/**").authenticated()
.anyRequest().denyAll())
.httpBasic(Customizer.withDefaults());
return http.build();
}
@Bean
AuthorizationManager<RequestAuthorizationContext> tenantReportAccess() {
return (authentication, context) -> {
Authentication current = authentication.get();
boolean hasPermission = current != null
&& current.getAuthorities().stream()
.anyMatch(authority ->
authority.getAuthority().equals("report:read"));
String tenantId =
context.getRequest().getHeader("X-Tenant-ID");
return new AuthorizationDecision(
hasPermission && tenantId != null && !tenantId.isBlank());
};
}
@Bean
UserDetailsService users() {
UserDetails alice = User.withUsername("alice")
.password("{noop}password")
.authorities("report:read")
.build();
UserDetails admin = User.withUsername("admin")
.password("{noop}password")
.authorities("ROLE_ADMIN")
.build();
return new InMemoryUserDetailsManager(alice, admin);
}
}
@RestController
class DemoController {
@GetMapping("/public/ping")
Map<String, String> ping() {
return Map.of("message", "pong");
}
@GetMapping("/api/reports/summary")
Map<String, String> report() {
return Map.of("scope", "tenant report");
}
@DeleteMapping("/api/users/{id}")
Map<String, String> deleteUser(@PathVariable String id) {
return Map.of("deleted", id);
}
}预期输出(启动日志关键行,时间可能不同):
Started AuthorizationDemoApplication in <TIME> seconds运行并验证授权结果
应用启动后,把 <PORT> 替换为实际端口;Spring Boot 默认通常为 8080。三个请求依次验证“权限加业务条件”“缺少业务条件”和“管理员角色”。
curl -i -u alice:password -H "X-Tenant-ID: tenant-a" http://localhost:<PORT>/api/reports/summary
curl -i -u alice:password http://localhost:<PORT>/api/reports/summary
curl -i -u admin:password -X DELETE http://localhost:<PORT>/api/users/42预期结果:
HTTP/1.1 200
Content-Type: application/json
{"scope":"tenant report"}
HTTP/1.1 403
HTTP/1.1 200
Content-Type: application/json
{"deleted":"42"}第一条请求同时满足 report:read 和 X-Tenant-ID,第二条缺少租户条件,因此即使拥有权限也会被拒绝;第三条通过 ROLE_ADMIN 满足 hasRole("ADMIN")。
自定义规则与边界
规则应遵循“具体路径在前、兜底规则在后”,并优先使用 anyRequest().denyAll() 实现默认拒绝。自定义授权管理器可以读取请求方法、路径、请求头和认证信息,但不要把复杂的数据归属查询全部堆进过滤器链,否则会增加每次请求的延迟和耦合。
生产系统应从数据库、JWT 或身份提供方加载权限,示例中的内存用户和 {noop} 密码仅用于本地验证。业务对象归属、审批状态等数据级规则更适合放到服务方法授权中,与请求级规则形成双层保护。