Closed rjbgaspar closed 1 year ago
Thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add a minimal sample that reproduces this issue if you feel this is a genuine bug.
Having said that, please note that for servlet environments, the class ServletOAuth2AuthorizedClientExchangeFilterFunction
should be used. See WebClient Integration for Servlet Environments for more information. If you feel I have misunderstood your question, please let me know and we can re-open if necessary.
I'm using 5.7.3 via Spring Boot security starters and the app was build using JHipster version 7.9.3
Describe the bug If a filter of type
ServerOAuth2AuthorizedClientExchangeFilterFunction
is used to make any request before any incoming web request (servlet) is received, this request is not process until a timeout stop it.The current filter is org.springframework.security.web.server.authentication.AuthenticationWebFilter and I think it's somehow related to the fact of the processor being unable to create the claims set.
NimbusReactiveJwtDecoder.java
The selector is created, but it never execute the
source.get(selector)
the log shows:If the app is started and there no communications between the microservices, if a web request is received it is correctly processed as shown in the log
To Reproduce This is my current configuration:
SecurityConfiguration.java
OAuth2ClientConfiguration.java
WebClientConfiguration .java
Expected behavior I spent several days trying to understand why this is happening, but I was not able to, despite I think it has something to do with createClaimsSet or with cachedJWKSet (ReactiveRemoteJWKSource). I honestly believe that the request should have an answer, e.g. not ending with timeout.