reactor-netty | TCP/HTTP/UDP/QUIC client/server with Reactor over Netty | Websocket library

I would propose to take a look in the RateLimiter direction. Maybe it does not work as expected, depending on the number of requests your application does over time. From the Javadoc for Ratelimiter: "It is important to note that the number of permits requested never affects the throttling of the request itself ... but it affects the throttling of the next request. I.e., if an expensive task arrives at an idle RateLimiter, it will be granted immediately, but it is the next request that will experience extra throttling, thus paying for the cost of the expensive task." Also helpful might be this discussion: github or github

I could imaginge there is some throttling adding up or other effect in the RateLimiter, i would try to play around with it and make sure this thing really works the way you want. Alternatively, consider using Spring @Scheduled to read from your queue. You might want to spice it up using embedded JMS for further goodies (message persistence etc).

I was facing the very same problem with azure dependencies last few days. Upgrading spring-boot-starter-parent to version 2.5.5 fixed it for me.

You have annotated your application with @EnableWebFlux. This indicates that you want to take complete control of WebFlux's configuration. This causes Spring Boot's auto-configuration of WebFlux to back off. Among other things, this means that it won't configure WebFlux to use the context's ObjectMapper.

You should either remove @EnableWebFlux to allow Spring Boot to auto-configure WebFlux or you should configure its codecs manually so that they use your ObjectMapper.

You have specified a redirect-uri for your client of /login. The page that says "Login with OAuth 2.0" is an auto-generated login page that Spring Security makes available by default under the /login endpoint. I don't think you intended to redirect there, but you currently have configured your client to do so.

The docs for OAuth 2.0 Login with WebFlux (Reactive) have recently been rewritten to align with the Servlet version, and are worth reading in their entirety.

Read the section of the docs on the Redirection Endpoint. Until you have a basic flow working, I'd recommend setting your redirect-uri to the default value of "{baseUrl}/login/oauth2/code/{registrationId}". Once things work, you can begin exploring how to customize this value. As the docs state, keep in mind that changing your redirect-uri property for a client also requires customizing the Redirection Endpoint in Spring Security to match.

If you also wish to customize the default Login Page, see the previous section of the docs, OAuth 2.0 Login Page.

The problem was occurring because the default authentication manager wasn't working for me, I had to implement one specifically for my problem.

So after some research I found out the exception is returned if no columns are returned in r2dbc. Issue was either insert was not happening or jooq could not return generated key. Turns out its the latter and it's a known jooq issue its documented very well here https://github.com/jOOQ/jOOQ/issues/2943 but there is a workaround for returning the generated value which is what I wanted in the first place. so below is the refactored code and its working now.

Having multiple @RequestBody is not possible. If you really need both original JSON and its serialized version the best you can do is receive the request body as a plain String and then convert it to the corresponding Java object as follows:

It seems that you have flyway dependency in your pom. When using @SpringbootTest, It will initialize the whole application context. According to the Springboot Autoconfigure mechanism, the application detects the Flyway module and tries to create a bean named flyway:

Error creating bean with name 'flyway'

And then when constructing the flyway bean, the flyway Factory needs a datasource bean.

I suppose these are false positives as reactor-netty-http did not had the vulnerability it was HttpObjectDecoder.java in Netty before 4.1.44. The regex provided by https://nvd.nist.gov/vuln/detail/CVE-2019-20444 are sometimes too unspecific.

According to the docs you can suppress the false positives following this guide: https://github.com/anchore/grype#specifying-matches-to-ignore

If you are using maven you could just add (but you don't have to because these are false positives):