Add RestEasy Reactive and OidcSecurity test

[sberyozkin]

Fixes #25722.

@geoand FYI, see TestSecurityLazyAuthTest. The RestEasy Classic based test runs here: https://github.com/quarkusio/quarkus/blob/main/integration-tests/smallrye-jwt-token-propagation/src/test/java/io/quarkus/it/keycloak/TestSecurityLazyAuthTest.java,

I've just copied that test and ProtectedJwtResource to integration-tests/oidc-token-propagation-reactive.

JwtSecurity extends TestSecurity and offers one option for supporting testing the endpoints which have an injected JsonWebtoken.
It is processed here: https://github.com/quarkusio/quarkus/blob/main/test-framework/security-jwt/src/main/java/io/quarkus/test/security/jwt/JwtTestSecurityIdentityAugmentorProducer.java

and this test augmentor is initiated from here:

https://github.com/quarkusio/quarkus/blob/main/test-framework/security/src/main/java/io/quarkus/test/security/QuarkusSecurityTestExtension.java#L88.

So this JwtTestSecurityIdentityAugmentorProducer adds a JsonWebToken instance to the current SecurityIdentity and this producer, https://github.com/quarkusio/quarkus/blob/main/extensions/oidc/runtime/src/main/java/io/quarkus/oidc/runtime/OidcJsonWebTokenProducer.java#L40, is expected to support the injection of JsonWebToken using this emulated token.

this test gives NPE, ProtectedJwtResource throws it because JsonWebToken remains null and is not injected.

Have a look please when you can get a chance

[geoand]

Thanks!

[sberyozkin]

@geoand Np at all, let me know please if I can help somehow, check some reactive resteasy code, etc

[geoand]

Will do!

[sberyozkin]

@geoand I've updated the test to use OidcSecurity instead as the OIDC JsonWebToken producer enforces JsonWebToken was indirectly created by quarkus-oidc. All works fine with RestEasy Reactive.

And, also, locally, I've modified integration-tests/smallrye-jwt-token-propagation to use RestEasy Reactive which uses JwtSecurity and it also works fine (I'm not sure it is worth adding a new integration test module just to test this case though).

So it is a Can't reproduce case

[geoand]

Understood, thanks for looking into it @sberyozkin!