响应式 X.509 认证

类似于 Servlet X.509 认证，响应式 X.509 认证过滤器允许从客户端提供的证书中提取认证令牌。

以下示例展示了响应式 X.509 安全配置

Java
Kotlin

@Bean
public SecurityWebFilterChain securityWebFilterChain(ServerHttpSecurity http) {
	http
		.x509(withDefaults())
		.authorizeExchange(exchanges -> exchanges
		    .anyExchange().permitAll()
		);
	return http.build();
}

@Bean
fun securityWebFilterChain(http: ServerHttpSecurity): SecurityWebFilterChain {
    return http {
        x509 { }
        authorizeExchange {
            authorize(anyExchange, authenticated)
        }
    }
}

在上述配置中，如果既未提供 principalExtractor 也未提供 authenticationManager，则会使用默认值。默认的主体提取器是 SubjectDnX509PrincipalExtractor，它从客户端提供的证书中提取 CN（通用名称）字段。默认的认证管理器是 ReactivePreAuthenticatedAuthenticationManager，它执行用户账户验证，检查由 principalExtractor 提取名称的用户账户是否存在，并且未被锁定、禁用或过期。

以下示例演示了如何覆盖这些默认值

Java
Kotlin

@Bean
public SecurityWebFilterChain securityWebFilterChain(ServerHttpSecurity http) {
	SubjectDnX509PrincipalExtractor principalExtractor =
	        new SubjectDnX509PrincipalExtractor();

	principalExtractor.setSubjectDnRegex("OU=(.*?)(?:,|$)");

	ReactiveAuthenticationManager authenticationManager = authentication -> {
		authentication.setAuthenticated("Trusted Org Unit".equals(authentication.getName()));
		return Mono.just(authentication);
	};

	http
		.x509(x509 -> x509
		    .principalExtractor(principalExtractor)
		    .authenticationManager(authenticationManager)
		)
		.authorizeExchange(exchanges -> exchanges
		    .anyExchange().authenticated()
		);
	return http.build();
}

@Bean
fun securityWebFilterChain(http: ServerHttpSecurity): SecurityWebFilterChain? {
    val customPrincipalExtractor = SubjectDnX509PrincipalExtractor()
    customPrincipalExtractor.setSubjectDnRegex("OU=(.*?)(?:,|$)")
    val customAuthenticationManager = ReactiveAuthenticationManager { authentication: Authentication ->
        authentication.isAuthenticated = "Trusted Org Unit" == authentication.name
        Mono.just(authentication)
    }
    return http {
        x509 {
            principalExtractor = customPrincipalExtractor
            authenticationManager = customAuthenticationManager
        }
        authorizeExchange {
            authorize(anyExchange, authenticated)
        }
    }
}

在上一个示例中，用户名是从客户端证书的 OU 字段而不是 CN 中提取的，并且根本不执行使用 ReactiveUserDetailsService 的账户查找。相反，如果提供的证书颁发给了名为“Trusted Org Unit”的 OU，则请求会被认证。

有关配置 Netty 和 WebClient 或 curl 命令行工具以使用双向 TLS 并启用 X.509 认证的示例，请参阅 github.com/spring-projects/spring-security-samples/tree/main/servlet/java-configuration/authentication/x509。