From cc7c3bfa1953d4901a999a972c1c6b1ed459b17c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Wacongne?= Date: Fri, 22 Nov 2024 08:26:03 -1000 Subject: [PATCH] Update README.MD --- README.MD | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.MD b/README.MD index 664549f3c..db6596d5f 100644 --- a/README.MD +++ b/README.MD @@ -99,7 +99,7 @@ Testing access control requires configuring the test security context. For that - build tests security context by yourself and populate it with stubbed / mocked authentications - **use annotations** to do it for you (this is where [spring-addons-oauth2-test](https://github.com/ch4mpy/spring-addons/tree/master/spring-addons-oauth2-test) jumps in) -Another important limitation of **the test `Authentication` factories for resource servers in `spring-security-test` is they ignore more security conf than necessary**. For instance, when a JWT decoder is used: +Also, **the test `Authentication` factories for resource servers in `spring-security-test` ignore more security conf than necessary**. For instance, when a JWT decoder is used: 1. decoded, validated, and turned into a `org.springframework.security.oauth2.jwt.Jwt` by a `JwtDecoder` 2. this `Jwt` (not JWT) is turned into something extending `AbstractAuthenticationToken` by an authentication converter 3. the `Authentication` instance is put in the security context