Skip to main content

Https Connection Android

Image
By User



I am doing a https post and I'm getting an exception of ssl exception Not trusted server certificate. If i do normal http it is working perfectly fine. Do I have to accept the server certificate somehow?




Labels:

Comments

  1. Tips For AllMarch 9, 2012 at 6:40 AM

    I'm making a guess, but if you want an actual handshake to occur, you have to let android know of your certificate. If you want to just accept no matter what, then use this pseudo-code to get what you need with the Apache HTTP Client:

    SchemeRegistry schemeRegistry = new SchemeRegistry ();

    schemeRegistry.register (new Scheme ("http",
    PlainSocketFactory.getSocketFactory (), 80));
    schemeRegistry.register (new Scheme ("https",
    new CustomSSLSocketFactory (), 443));

    ThreadSafeClientConnManager cm = new ThreadSafeClientConnManager (
    params, schemeRegistry);


    return new DefaultHttpClient (cm, params);


    CustomSSLSocketFactory:

    public class CustomSSLSocketFactory extends org.apache.http.conn.ssl.SSLSocketFactory
    {
    private SSLSocketFactory FACTORY = HttpsURLConnection.getDefaultSSLSocketFactory ();

    public CustomSSLSocketFactory ()
    {
    super(null);
    try
    {
    SSLContext context = SSLContext.getInstance ("TLS");
    TrustManager[] tm = new TrustManager[] { new FullX509TrustManager () };
    context.init (null, tm, new SecureRandom ());

    FACTORY = context.getSocketFactory ();
    }
    catch (Exception e)
    {
    e.printStackTrace();
    }
    }

    public Socket createSocket() throws IOException
    {
    return FACTORY.createSocket();
    }

    // TODO: add other methods like createSocket() and getDefaultCipherSuites().
    // Hint: they all just make a call to member FACTORY
    }


    FullX509TrustManager is a class that implements javax.net.ssl.X509TrustManager, yet none of the methods actually perform any work, get a sample here.

    Good Luck!

    ReplyDelete
  2. Tips For AllMarch 9, 2012 at 6:40 AM

    This is what I am doing. It simply doesn't check the certificate anymore.

    // always verify the host - dont check for certificate
    final static HostnameVerifier DO_NOT_VERIFY = new HostnameVerifier() {
    public boolean verify(String hostname, SSLSession session) {
    return true;
    }
    };

    /**
    * Trust every server - dont check for any certificate
    */
    private static void trustAllHosts() {
    // Create a trust manager that does not validate certificate chains
    TrustManager[] trustAllCerts = new TrustManager[] { new X509TrustManager() {
    public java.security.cert.X509Certificate[] getAcceptedIssuers() {
    return new java.security.cert.X509Certificate[] {};
    }

    public void checkClientTrusted(X509Certificate[] chain,
    String authType) throws CertificateException {
    }

    public void checkServerTrusted(X509Certificate[] chain,
    String authType) throws CertificateException {
    }
    } };

    // Install the all-trusting trust manager
    try {
    SSLContext sc = SSLContext.getInstance("TLS");
    sc.init(null, trustAllCerts, new java.security.SecureRandom());
    HttpsURLConnection
    .setDefaultSSLSocketFactory(sc.getSocketFactory());
    } catch (Exception e) {
    e.printStackTrace();
    }
    }


    and

    HttpURLConnection http = null;

    if (url.getProtocol().toLowerCase().equals("https")) {
    trustAllHosts();
    HttpsURLConnection https = (HttpsURLConnection) url.openConnection();
    https.setHostnameVerifier(DO_NOT_VERIFY);
    http = https;
    } else {
    http = (HttpURLConnection) url.openConnection();
    }

    ReplyDelete
  3. Tips For AllMarch 9, 2012 at 6:40 AM

    While trying to answer this question I found a better tutorial. With it you don't have to compromise the certificate check.

    http://blog.crazybob.org/2010/02/android-trusting-ssl-certificates.html

    *I did not write this but thanks to Bob Lee for the work

    ReplyDelete
  4. Tips For AllMarch 9, 2012 at 6:40 AM

    You can also look at my blog article, very similar to crazybobs.

    This solution also doesn't compromise certificate checking and explains how to add the trusted certs in your own keystore.

    http://blog.antoine.li/index.php/2010/10/android-trusting-ssl-certificates/

    ReplyDelete
  5. Tips For AllMarch 9, 2012 at 6:40 AM

    None of these worked for me (aggravated by the Thawte bug as well). Eventually I got it fixed with Self Signed SSL acceptance Android and Custom SSL handling stopped working on Android 2.2 FroYo

    ReplyDelete
  6. Tips For AllMarch 9, 2012 at 6:40 AM

    I don't know about the Android specifics for ssl certificates, but it would make sense that Android won't accept a self signed ssl certificate off the bat. I found this post from android forums which seems to be addressing the same issue:
    http://androidforums.com/android-applications/950-imap-self-signed-ssl-certificates.html

    ReplyDelete
  7. Tips For AllMarch 9, 2012 at 6:40 AM

    may this thread help, but i can not tell if it works will latest API :

    http://groups.google.com/group/android-developers/browse%5Fthread/thread/1ac2b851e07269ba/c7275f3b28ad8bbc?#c7275f3b28ad8bbc

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

By User
I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?
30 comments
Read more