20K Java+AI 岗位高频考点 — 安全认证是所有系统的基石。覆盖OAuth2四种授权模式、JWT原理与实战、Spring Security 6配置、SSO单点登录、微服务间安全通信、RBAC权限模型。
常见认证方式:
| 维度 | Session | Token(JWT) |
|---|---|---|
| 存储位置 | 服务端 | 客户端 |
| 扩展性 | 差(需共享Session) | 好(无状态) |
| 安全性 | 较高(服务端控制) | 需注意Token泄露 |
| 注销 | 删除Session即可 | 较难(需黑名单) |
| 适用场景 | 传统Web | API/微服务 |
JWT = Header.Payload.Signature
Header: {"alg":"HS256","typ":"JWT"}
Payload: {"sub":"123","name":"张三","exp":1700000000}
Signature: HMACSHA256(base64(header) + "." + base64(payload), secret)
Java生成JWT:
// JJWT库
String token = Jwts.builder()
.setSubject(userId.toString())
.claim("name", user.getName())
.claim("roles", user.getRoles())
.setIssuedAt(new Date())
.setExpiration(new Date(System.currentTimeMillis() + 3600 * 1000)) // 1小时
.signWith(SignatureAlgorithm.HS256, secretKey)
.compact();
JWT的安全问题:
登录 → 返回 Access Token(短期) + Refresh Token(长期)
Access Token过期 → 用Refresh Token换新Access Token
Refresh Token过期 → 重新登录
优势:Access Token短有效期(15min)降低泄露风险
Refresh Token长有效期(7天)减少登录频率
@PostMapping("/refresh")
public TokenResponse refresh(@RequestBody RefreshRequest request) {
String refreshToken = request.getRefreshToken();
// 1. 验证Refresh Token
Claims claims = jwtUtil.parseToken(refreshToken);
if (claims == null) {
throw new UnauthorizedException("Refresh Token无效");
}
// 2. 生成新Access Token
String newAccessToken = jwtUtil.generateAccessToken(claims.getSubject());
// 3. 轮换Refresh Token(可选,更安全)
String newRefreshToken = jwtUtil.generateRefreshToken(claims.getSubject());
return new TokenResponse(newAccessToken, newRefreshToken);
}
| 模式 | 流程 | 适用场景 |
|---|---|---|
| 授权码模式 | 用户→授权页→回调带code→后端换token | Web应用(最安全) |
| 隐式模式 | 用户→授权页→回调直接带token | SPA(已不推荐) |
| 密码模式 | 用户直接给密码→换token | 内部可信应用 |
| 客户端模式 | 客户端ID+Secret→换token | 服务间调用 |
1. 用户点击"微信登录"
→ 重定向到微信授权页:https://open.weixin.qq.com/oauth2/authorize?response_type=code&client_id=xxx&redirect_uri=xxx
2. 用户同意授权
→ 微信回调redirect_uri并携带code:https://myapp.com/callback?code=AUTH_CODE
3. 后端用code换token
→ POST https://api.weixin.qq.com/sns/oauth2/access_token?code=AUTH_CODE&client_id=xxx&client_secret=xxx
4. 获取用户信息
→ GET https://api.weixin.qq.com/sns/userinfo?access_token=TOKEN&openid=OPENID
@Configuration
public class AuthorizationServerConfig {
@Bean
public RegisteredClientRepository registeredClientRepository() {
RegisteredClient webClient = RegisteredClient.withId(UUID.randomUUID().toString())
.clientId("web-app")
.clientSecret("{noop}secret") // 生产用bcrypt
.clientAuthenticationMethod(ClientAuthenticationMethod.CLIENT_SECRET_BASIC)
.authorizationGrantType(AuthorizationGrantType.AUTHORIZATION_CODE)
.authorizationGrantType(AuthorizationGrantType.REFRESH_TOKEN)
.redirectUri("http://localhost:8080/callback")
.scope("read").scope("write")
.clientSettings(ClientSettings.builder().requireAuthorizationConsent(true).build())
.tokenSettings(TokenSettings.builder()
.accessTokenTimeToLive(Duration.ofMinutes(15))
.refreshTokenTimeToLive(Duration.ofDays(7))
.build())
.build();
return new InMemoryRegisteredClientRepository(webClient);
}
}
@Configuration
@EnableWebSecurity
public class ResourceServerConfig {
@Bean
SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
return http
.authorizeHttpRequests(auth -> auth
.requestMatchers("/public/**").permitAll()
.requestMatchers("/api/**").authenticated()
.requestMatchers("/api/admin/**").hasRole("ADMIN")
)
.oauth2ResourceServer(oauth2 -> oauth2
.jwt(jwt -> jwt
.jwkSetUri("http://auth-server:9000/oauth2/jwks")
.jwtAuthenticationConverter(grantedAuthoritiesExtractor())
)
)
.sessionManagement(session -> session
.sessionCreationPolicy(SessionCreationPolicy.STATELESS))
.build();
}
// 从JWT的scope/roles字段提取权限
private JwtAuthenticationConverter grantedAuthoritiesExtractor() {
JwtAuthenticationConverter converter = new JwtAuthenticationConverter();
converter.setJwtGrantedAuthoritiesConverter(jwt -> {
List<String> roles = jwt.getClaimAsStringList("roles");
return roles.stream()
.map(r -> new SimpleGrantedAuthority("ROLE_" + r))
.collect(Collectors.toList());
});
return converter;
}
}
方案一:Token透传
// 网关验证Token后,将用户信息放入Header透传
@Component
public class AuthFilter implements GlobalFilter {
@Override
public Mono<Void> filter(ServerWebExchange exchange, GatewayFilterChain chain) {
String token = exchange.getRequest().getHeaders().getFirst("Authorization");
if (token == null || !jwtUtil.validate(token)) {
exchange.getResponse().setStatusCode(HttpStatus.UNAUTHORIZED);
return exchange.getResponse().setComplete();
}
// 解析Token,放入Header透传
String userId = jwtUtil.getUserId(token);
ServerHttpRequest request = exchange.getRequest().mutate()
.header("X-User-Id", userId)
.header("X-User-Roles", jwtUtil.getRoles(token))
.build();
return chain.filter(exchange.mutate().request(request).build());
}
}
方案二:内部服务间用mTLS/Service Token
-- 用户-角色-权限
CREATE TABLE user_role (user_id BIGINT, role_id BIGINT);
CREATE TABLE role_permission (role_id BIGINT, permission VARCHAR(64));
-- 权限编码示例
-- user:read, user:write, order:read, order:write, order:cancel
-- 或资源:操作格式
// Spring Security注解
@PreAuthorize("hasAuthority('order:write')")
@PostMapping("/orders")
public OrderDTO createOrder(@RequestBody CreateOrderRequest req) { ... }
@PreAuthorize("hasRole('ADMIN')")
@DeleteMapping("/users/{id}")
public void deleteUser(@PathVariable Long id) { ... }
基于OAuth2的SSO:
1. 用户访问app1.com → 未登录 → 重定向到sso.com
2. sso.com登录成功 → 设置sso.com的Cookie → 回调app1.com带code
3. app1.com用code换token → 登录成功
4. 用户访问app2.com → 未登录 → 重定向到sso.com
5. sso.com有Cookie → 自动授权 → 回调app2.com带code
6. app2.com用code换token → 登录成功(无需再输入密码)
1. HTTPS:传输加密
2. HttpOnly Cookie:防止XSS读取
3. 短有效期:Access Token 15分钟
4. IP绑定:Token绑定客户端IP
5. 设备指纹:Token绑定设备
6. Token黑名单:注销时加入黑名单
// Token黑名单(Redis实现)
@PostMapping("/logout")
public void logout(@RequestHeader("Authorization") String authHeader) {
String token = authHeader.replace("Bearer ", "");
long ttl = jwtUtil.getExpiration(token) - System.currentTimeMillis();
if (ttl > 0) {
redisTemplate.opsForValue().set("token:blacklist:" + token, "1", ttl, TimeUnit.MILLISECONDS);
}
}
// 过滤器中检查黑名单
public boolean isBlacklisted(String token) {
return redisTemplate.hasKey("token:blacklist:" + token);
}
CSRF:恶意网站利用已登录用户的Cookie发起请求。
防御:
XSS:注入恶意脚本到页面。
防御:
// HMAC签名验证
public class ApiSignInterceptor implements HandlerInterceptor {
@Override
public boolean preHandle(HttpServletRequest request, HttpServletResponse response, Object handler) {
String timestamp = request.getHeader("X-Timestamp");
String nonce = request.getHeader("X-Nonce");
String sign = request.getHeader("X-Sign");
// 1. 时间戳校验(防重放)
if (Math.abs(System.currentTimeMillis() - Long.parseLong(timestamp)) > 5 * 60 * 1000) {
throw new SecurityException("请求过期");
}
// 2. 验签
String body = StreamUtils.copyToString(request.getInputStream(), StandardCharsets.UTF_8);
String expectedSign = HmacUtils.hmacSha256Hex(apiSecret, timestamp + nonce + body);
if (!expectedSign.equals(sign)) {
throw new SecurityException("签名校验失败");
}
return true;
}
}
// Spring Boot + Redis限流
@Component
public class RateLimitInterceptor implements HandlerInterceptor {
@Autowired StringRedisTemplate redisTemplate;
@Override
public boolean preHandle(HttpServletRequest request, HttpServletResponse response, Object handler) {
String key = "rate_limit:" + getClientId(request) + ":" + request.getRequestURI();
Long count = redisTemplate.opsForValue().increment(key);
if (count == 1) {
redisTemplate.expire(key, 1, TimeUnit.SECONDS);
}
if (count > 100) { // 每秒100次
response.setStatus(429);
return false;
}
return true;
}
}
| 维度 | JWT | OAuth2 Token |
|---|---|---|
| 格式 | 自包含的JSON | 可以是任意格式 |
| 验证方式 | 本地验签 | 需要调用授权服务器 |
| 撤销 | 困难(需黑名单) | 容易(授权服务器撤销) |
| 信息量 | 可携带用户信息 | 通常只有ID |
| 适用 | 微服务内部 | 对外开放平台 |
认证中心(Auth Server):
├── OAuth2授权服务器(Spring Authorization Server)
├── 用户认证(密码/短信/OAuth2第三方)
├── Token管理(JWT签发/刷新/撤销)
└── 统一登录页面
各业务服务(Resource Server):
├── 验证JWT Token
├── RBAC权限校验
└── 审计日志
API网关(Gateway):
├── Token校验+解析
├── 用户信息透传
└── 限流+黑名单
外部 → WAF(Web应用防火墙)
→ CDN(Ddos防护)
→ API网关(认证+限流)
→ 服务间(mTLS/Token)
→ 应用层(RBAC+审计)
→ 数据层(加密+脱敏)
// Lambda DSL(6.x推荐)
http.authorizeHttpRequests(auth -> auth
.requestMatchers("/public/**").permitAll()
.requestMatchers("/api/**").authenticated()
.anyRequest().denyAll()
);
// 废弃WebSecurityConfigurerAdapter
// 改用组件式@Bean配置
认证三件套:OAuth2做授权、JWT做令牌、RBAC做权限
>
Token安全三原则:HTTPS传输、短有效期、黑名单撤销
>
微服务安全三层:网关认证→服务间Token→应用层权限
>
选型口诀:内部用JWT、开放用OAuth2、SSO用授权码模式