netty-http | Netty based HTTP service with JAX-RS | HTTP library

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.

You can try setting the throwExceptionOnFailure option to false. Http components in camel have this enabled on default, probably so that failures can easily be caught and handled like any other exceptions in camel.

When its enabled you can get the Exception and details about the exception through Exchange properties which in this chase you can probably cast to NettyHttpOperationFailedException to get more information about it.

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):

It seems to me that you are sending a message property that is not expected at all by the service you are calling.

You are setting BulkSmsRequestResourceTest as both the body request and also the body response. Are you sure that the server is expecting message property in the request and will also include message in the response?

Your additional code just shows this is in fact true. Your server is answering with a simple String ("message success sended"), but you are expecting it to be an object (BulkSmsRequestResourceTest). Please update your code to the following one:

Bear in mind header validation is in place for a reason by default - disabling it can leave you open to security vulnerabilities like CWE-113.

That being said, yes, if you have a genuine reason to then you can disable header validation on the HttpClient side:

With Reactor Netty you have to do the opposite logic: Send these bytes when you receive those bytes. You should never block in the event loop. The example above can be rewritten like the one below:

Use