Expected Behavior
When I define a bean of type ReactiveJwtAuthenticationConverter, I would expect it to be considered in the OAuth2 Resource Server configuration automatically like it happens with its imperative counterpart (JwtAuthenticationConverter).
Current Behavior
When I define a bean of type ReactiveJwtAuthenticationConverter, it's not considered in the OAuth2 Resource Server configuration. Instead, it requires explicit definition through the DSL as follows.
.oauth2ResourceServer(oauth2 -> oauth2.jwt(jwt ->
jwt.jwtAuthenticationConverter(jwtAuthenticationConverter())))
Context
It would be nice to align the behaviour between reactive and non-reactive applications since it could generate some confusion.
Proposed solution: #9699