The problem on production was the certifcates doesn't match with the host used on my JdbcSourceConfig configuration. If they match you will be able to use update-crypto-policies --set LEGACY

Note. Don't forget to be careful with the security, it's better to use a different approach to handle this situation instead of what I'm applying. And also set your logger level correctly because mine was not properly configured and that was the reason why I didn't catch the error before.

Regards,