Coverity giving High Impact Security Issue in API Client code for applySslSettings() method

Coverity is raising security issues for TrustManager in highlighted code below

TrustManager[] trustManagers = null;
HostnameVerifier hostnameVerifier = null;
if (!verifyingSsl) {
TrustManager trustAll = new X509TrustManager() {
@Override
public void checkClientTrusted(X509Certificate[] chain, String authType) throws CertificateException {}
@Override
public void checkServerTrusted(X509Certificate[] chain, String authType) throws CertificateException {}
@Override
public X509Certificate[] getAcceptedIssuers() { return null; }
};
SSLContext sslContext = SSLContext.getInstance("TLS");
trustManagers = new TrustManager[]{ trustAll };
hostnameVerifier = new HostnameVerifier() {
@Override
public boolean verify(String hostname, SSLSession session) { return true; }
};

Start by tracing applySslSettings() in generatedChild/src/main/java/com/amdocs/oss/sfo/serviceordermanager/child/ApiClient.java and generated/src/main/java/io/swagger/client/ApiClient.java. Review the reported checkClientTrusted, checkServerTrusted, and verify methods against the Coverity findings; done means the listed insecure SSL/TLS findings are addressed in the affected generated client code.