trustmanager

Google has advised that I have an unsafe implementation of the interface X509TrustManager in my Android application and need to change my code as follows: To properly handle SSL certificate validation, change your code in the checkServerTrusted method of your custom X509TrustManager interface to raise either CertificateException or IllegalArgumentException whenever the certificate presented by the server does not meet your expectations. For technical questions, you can post to Stack Overflow and use the tags “android-security” and “TrustManager.” How can the following code be modified to fix

I hava an app in Google Play, I received a mail from Google saying that: Your app(s) listed at the end of this email use an unsafe implementation of the interface X509TrustManager. Specifically, the implementation ignores all SSL certificate validation errors when establishing an HTTPS connection to a remote host, thereby making your app vulnerable to man-in-the-middle attacks. To properly handle SSL certificate validation, change your code in the checkServerTrusted method of your custom X509TrustManager interface to raise either CertificateException or IllegalArgumentException whenever the

Before making the question, I found some links, which I checked, one by one, and none of them, gives me a solution: well-kown CA HTTPS request using volley accept all SSL certificates No peer certificate Exception - Volley and Android with self signed certificate Node.js (Socket.io) Socket.io + SSL + self-signed CA certificate gives error when connecting Self-Signed Certificate "MANUALLY" imported: Android SSL HTTP Request using self signed cert and CA The only link which I have found until now, is this one, which gives two approaches: Making a HTTPS request using Android Volley 1º Instructs