2011-03-05 73 views
31

我在tomcat中启用了https并为服务器认证拥有一个自签名证书。我使用Apache httpClient创建了一个http客户端。我已经设置了一个加载服务器证书的信任管理器。 http客户端可以连接服务器没有问题。要查看是怎么回事我启用调试:使用Apache httpclient进行https https

System.setProperty("javax.net.debug", "ssl"); 

我看到了,我无法理解在所有的情况如下:

*** 
adding as trusted cert: 
    Subject: CN=Me, OU=MyHouse, O=Home, L=X, ST=X, C=BB 
    Issuer: CN=Me, OU=MyHouse, O=Home, L=X, ST=X, C=BB 
    Algorithm: RSA; Serial number: 0x4d72356b 
    Valid from Sat Mar 05 15:06:51 EET 2011 until Fri Jun 03 16:06:51 EEST 2011 

我的证书显示,并添加到信任库(因为我看到) 。然后:

trigger seeding of SecureRandom 
done seeding SecureRandom 

这里是部分来自调试跟踪我不明白:

trustStore is: C:\Program Files\Java\jre6\lib\security\cacerts 
trustStore type is : jks 
trustStore provider is : 
init truststore 
adding as trusted cert: 
    Subject: CN=SwissSign Platinum CA - G2, O=SwissSign AG, C=CH 
    Issuer: CN=SwissSign Platinum CA - G2, O=SwissSign AG, C=CH 
    Algorithm: RSA; Serial number: 0x4eb200670c035d4f 
    Valid from Wed Oct 25 11:36:00 EEST 2006 until Sat Oct 25 11:36:00 EEST 2036 

adding as trusted cert: 
    Subject: [email protected], CN=http://www.valicert.com/, OU=ValiCert Class 1 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network 
    Issuer: [email protected], CN=http://www.valicert.com/, OU=ValiCert Class 1 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network 
    Algorithm: RSA; Serial number: 0x1 
    Valid from Sat Jun 26 01:23:48 EEST 1999 until Wed Jun 26 01:23:48 EEST 2019 

看来,它也采用了默认的Java信任库!我的问题是为什么会发生这种情况?

在我的代码中,我明确指定要使用的特定信任存储(通过truststoremanagers)。我期待只有这个被使用。似乎我的truststore和java的默认都被使用了。这是应该如何工作?

UPDATE:
我试过如下:

System.out.println("TMF No:"+tmf.getTrustManagers().length); 
System.out.println("Class is "+tmf.getTrustManagers()[0].getClass().getName()); 

我想,我应该看到2个信任管理器,因为2个密钥库(我和Java的默认显示使用)。
但结果只有1个信任管理器!

TMF No:1 
Class is com.sun.net.ssl.internal.ssl.X509TrustManagerImpl 

UPDATE2:正如你在代码中看到波纹管我指定我keystore.My意料的是,这仅应使用(不是这个 CACERT以及)

HttpClient client = new DefaultHttpClient(); 
    SSLContext sslContext = SSLContext.getInstance("TLS");  

    TrustManagerFactory tmf = TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm()); 
    KeyStore ks = KeyStore.getInstance("JKS"); 
    File trustFile = new File("clientTrustStore.jks"); 
    ks.load(new FileInputStream(trustFile), null); 
    tmf.init(ks); 
    sslContext.init(null, tmf.getTrustManagers(),null); 
    SSLSocketFactory sf = new SSLSocketFactory(sslContext); 
    sf.setHostnameVerifier(SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER); 
    Scheme scheme = new Scheme("https", sf, 443); 
    client.getConnectionManager().getSchemeRegistry().register(scheme); 
    httpGet = new HttpGet("https://localhost:8443/myApp"); 
    HttpResponse httpResponse = client.execute(httpGet); 

不对我来说没有意义。

回答

23

我放在一起本次测试的应用程序使用HTTP测试框架来自Apache HttpClient的包来重现问题:

ClassLoader cl = HCTest.class.getClassLoader(); 
URL url = cl.getResource("test.keystore"); 
KeyStore keystore = KeyStore.getInstance("jks"); 
char[] pwd = "nopassword".toCharArray(); 
keystore.load(url.openStream(), pwd); 

TrustManagerFactory tmf = TrustManagerFactory.getInstance(
     TrustManagerFactory.getDefaultAlgorithm()); 
tmf.init(keystore); 
TrustManager[] tm = tmf.getTrustManagers(); 

KeyManagerFactory kmfactory = KeyManagerFactory.getInstance(
     KeyManagerFactory.getDefaultAlgorithm()); 
kmfactory.init(keystore, pwd); 
KeyManager[] km = kmfactory.getKeyManagers(); 

SSLContext sslcontext = SSLContext.getInstance("TLS"); 
sslcontext.init(km, tm, null); 

LocalTestServer localServer = new LocalTestServer(sslcontext); 
localServer.registerDefaultHandlers(); 

localServer.start(); 
try { 

    DefaultHttpClient httpclient = new DefaultHttpClient(); 
    TrustStrategy trustStrategy = new TrustStrategy() { 

     public boolean isTrusted(X509Certificate[] chain, String authType) throws CertificateException { 
      for (X509Certificate cert: chain) { 
       System.err.println(cert); 
      } 
      return false; 
     } 

    }; 

    SSLSocketFactory sslsf = new SSLSocketFactory("TLS", null, null, keystore, null, 
      trustStrategy, new AllowAllHostnameVerifier()); 
    Scheme https = new Scheme("https", 443, sslsf); 
    httpclient.getConnectionManager().getSchemeRegistry().register(https); 

    InetSocketAddress address = localServer.getServiceAddress(); 
    HttpHost target1 = new HttpHost(address.getHostName(), address.getPort(), "https"); 
    HttpGet httpget1 = new HttpGet("/random/100"); 
    HttpResponse response1 = httpclient.execute(target1, httpget1); 
    System.err.println(response1.getStatusLine()); 
    HttpEntity entity1 = response1.getEntity(); 
    EntityUtils.consume(entity1); 
    HttpHost target2 = new HttpHost("www.verisign.com", 443, "https"); 
    HttpGet httpget2 = new HttpGet("/"); 
    HttpResponse response2 = httpclient.execute(target2, httpget2); 
    System.err.println(response2.getStatusLine()); 
    HttpEntity entity2 = response2.getEntity(); 
    EntityUtils.consume(entity2); 
} finally { 
    localServer.stop(); 
} 

即使Sun的JSSE实现出于某种原因总是从默认信任存储中读取信任材料,但似乎并未将其添加到SSL上下文中并影响SSL握手过程中的信任验证过程。

下面是测试应用程序的输出。正如您所看到的,第一个请求成功,而第二个请求失败,因为连接到www.verisign.com被拒绝为不可信。

[ 
[ 
    Version: V1 
    Subject: CN=Simple Test Http Server, OU=Jakarta HttpClient Project, O=Apache Software Foundation, L=Unknown, ST=Unknown, C=Unknown 
    Signature Algorithm: SHA1withDSA, OID = 1.2.840.10040.4.3 

    Key: Sun DSA Public Key 
    Parameters:DSA 
    p:  fd7f5381 1d751229 52df4a9c 2eece4e7 f611b752 3cef4400 c31e3f80 b6512669 
    455d4022 51fb593d 8d58fabf c5f5ba30 f6cb9b55 6cd7813b 801d346f f26660b7 
    6b9950a5 a49f9fe8 047b1022 c24fbba9 d7feb7c6 1bf83b57 e7c6a8a6 150f04fb 
    83f6d3c5 1ec30235 54135a16 9132f675 f3ae2b61 d72aeff2 2203199d d14801c7 
    q:  9760508f 15230bcc b292b982 a2eb840b f0581cf5 
    g:  f7e1a085 d69b3dde cbbcab5c 36b857b9 7994afbb fa3aea82 f9574c0b 3d078267 
    5159578e bad4594f e6710710 8180b449 167123e8 4c281613 b7cf0932 8cc8a6e1 
    3c167a8b 547c8d28 e0a3ae1e 2bb3a675 916ea37f 0bfa2135 62f1fb62 7a01243b 
    cca4f1be a8519089 a883dfe1 5ae59f06 928b665e 807b5525 64014c3b fecf492a 

    y: 
    f0cc639f 702fd3b1 03fa8fa6 676c3756 ea505448 23cd1147 fdfa2d7f 662f7c59 
    a02ddc1a fd76673e 25210344 cebbc0e7 6250fff1 a814a59f 30ff5c7e c4f186d8 
    f0fd346c 29ea270d b054c040 c74a9fc0 55a7020f eacf9f66 a0d86d04 4f4d23de 
    7f1d681f 45c4c674 5762b71b 808ded17 05b74baf 8de3c4ab 2ef662e3 053af09e 

    Validity: [From: Sat Dec 11 14:48:35 CET 2004, 
       To: Tue Dec 09 14:48:35 CET 2014] 
    Issuer: CN=Simple Test Http Server, OU=Jakarta HttpClient Project, O=Apache Software Foundation, L=Unknown, ST=Unknown, C=Unknown 
    SerialNumber: [ 41bafab3] 

] 
    Algorithm: [SHA1withDSA] 
    Signature: 
0000: 30 2D 02 15 00 85 BE 6B D0 91 EF 34 72 05 FF 1A 0-.....k...4r... 
0010: DB F6 DE BF 92 53 9B 14 27 02 14 37 8D E8 CB AC .....S..'..7.... 
0020: 4E 6C 93 F2 1F 7D 20 A1 2D 6F 80 5F 58 AE 33  Nl.... .-o._X.3 

] 
HTTP/1.1 200 OK 
[ 
[ 
    Version: V3 
    Subject: CN=www.verisign.com, OU=" Production Security Services", O="VeriSign, Inc.", STREET=487 East Middlefield Road, L=Mountain View, ST=California, OID.2.5.4.17=94043, C=US, SERIALNUMBER=2497886, OID.2.5.4.15="V1.0, Clause 5.(b)", OID.1.3.6.1.4.1.311.60.2.1.2=Delaware, OID.1.3.6.1.4.1.311.60.2.1.3=US 
    Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5 

    Key: Sun RSA public key, 2048 bits 
    modulus: 20699622354183393041832954221256409980425015218949582822286196083815087464214375375678538878841956356687753084333860738385445545061253653910861690581771234068858443439641948884498053425403458465980515883570440998475638309355278206558031134532548167239684215445939526428677429035048018486881592078320341210422026566944903775926801017506416629554190534665876551381066249522794321313235316733139718653035476771717662585319643139144923795822646805045585537550376512087897918635167815735560529881178122744633480557211052246428978388768010050150525266771462988042507883304193993556759733514505590387262811565107773578140271 
    public exponent: 65537 
    Validity: [From: Wed May 26 02:00:00 CEST 2010, 
       To: Sat May 26 01:59:59 CEST 2012] 
    Issuer: CN=VeriSign Class 3 Extended Validation SSL SGC CA, OU=Terms of use at https://www.verisign.com/rpa (c)06, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US 
    SerialNumber: [ 53d2bef9 24a7245e 83ca01e4 6caa2477] 

Certificate Extensions: 10 
[1]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false 
AuthorityInfoAccess [ 
    [accessMethod: 1.3.6.1.5.5.7.48.1 
    accessLocation: URIName: http://EVIntl-ocsp.verisign.com, accessMethod: 1.3.6.1.5.5.7.48.2 
    accessLocation: URIName: http://EVIntl-aia.verisign.com/EVIntl2006.cer] 
] 

... 

] 
Exception in thread "main" javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated 
    at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:345) 
    at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) 
    at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:446) 
... 
+0

这是一个很好的测试。感谢您的帮助 – Cratylus 2011-03-09 20:52:57

+0

嗨Oleg,我面临类似的问题,但只有当我发送POST请求,而不是通过GET。任何见解? – Abhishek 2011-05-09 06:45:48

+0

那么,在这个地方是否存在一个可以追踪解决方案的bug? – pulkitsinghal 2013-01-08 17:20:17

2

根据需要指定密钥存储在documentation

Protocol authhttps = new Protocol("https", 
     new AuthSSLProtocolSocketFactory(
      new URL("file:my.keystore"), "mypassword", 
      new URL("file:my.truststore"), "mypassword"), 443); 

HttpClient client = new HttpClient(); 
client.getHostConfiguration().setHost("localhost", 443, authhttps); 
+0

修改后的版本http://hc.apache.org/httpcomponents-客户GA /。我正在做类似的计划Scheme = new Scheme(“https”,443,sf); ();和sf是'SSLSocketFactory sf =新的SSLSocketFactory(sslContext,SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER);'和在sslContext中我已经设置了我的信任存储管理器。我可以更新如果它会帮助 – Cratylus 2011-03-05 21:33:40

+0

@ user384706我有些困惑。问题是_client_正在使用2个TrustManagers(SSLContext.init不应该这么做),还是它的行为奇怪的tomcat _server_? – extraneon 2011-03-05 21:47:29

+0

Tomcat.Tomcat没有问题发送我配置的证书。问题出现在客户端部分。我指定了一个可信的trustore,期望仅使用它。调试信息显示我的以及默认的java信任库。我更新了我的帖子,在客户端部分 – Cratylus 2011-03-05 21:59:05

4

当我使用Apache HTTP客户端4.3时,我使用池连接管理器或基本连接管理器连接到HTTP客户端。我注意到,从使用java SSL调试,这些类加载cacerts信任存储,而不是我已经编程指定的。

PoolingHttpClientConnectionManager cm = new PoolingHttpClientConnectionManager(); 
BasicHttpClientConnectionManager cm = new BasicHttpClientConnectionManager(); 
builder.setConnectionManager(cm); 

我想使用它们,但最终删除它们并创建一个没有它们的HTTP客户端。请注意,构建器是一个HttpClientBuilder。

我使用Java SSL调试标志运行我的程序时已确认,并在调试器中停止。我使用-Djavax.net.debug = ssl作为VM参数。我在调试器中停止了我的代码,当上面的* ClientConnectionManager被构造时,cacerts文件将被加载。

+2

非常感谢你。我不能为我的生活找出问题所在,然后在阅读后发现,如果您已经通过连接管理器,构建器基本上忽略了您提供的sslContext。 – 2015-04-15 10:34:48

4

这是对我工作:

KeyStore keyStore = KeyStore.getInstance("PKCS12"); 
    FileInputStream instream = new FileInputStream(new File("client-p12-keystore.p12")); 
    try { 
     keyStore.load(instream, "password".toCharArray()); 
    } finally { 
     instream.close(); 
    } 

    // Trust own CA and all self-signed certs 
    SSLContext sslcontext = SSLContexts.custom() 
     .loadKeyMaterial(keyStore, "password".toCharArray()) 
     //.loadTrustMaterial(trustStore, new TrustSelfSignedStrategy()) 
     .build(); 
    // Allow TLSv1 protocol only 
    SSLConnectionSocketFactory sslsf = new SSLConnectionSocketFactory(
     sslcontext, 
     new String[] { "TLSv1" }, 
     null, 
     SSLConnectionSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER); //TODO 
    CloseableHttpClient httpclient = HttpClients.custom() 
     .setHostnameVerifier(SSLConnectionSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER) //TODO 
     .setSSLSocketFactory(sslsf) 
     .build(); 
    try { 

     HttpGet httpget = new HttpGet("https://localhost:8443/secure/index"); 

     System.out.println("executing request" + httpget.getRequestLine()); 

     CloseableHttpResponse response = httpclient.execute(httpget); 
     try { 
      HttpEntity entity = response.getEntity(); 

      System.out.println("----------------------------------------"); 
      System.out.println(response.getStatusLine()); 
      if (entity != null) { 
       System.out.println("Response content length: " + entity.getContentLength()); 
      } 
      EntityUtils.consume(entity); 
     } finally { 
      response.close(); 
     } 
    } finally { 
     httpclient.close(); 
    } 
} 

这段代码是我没有使用commons.I正在使用的http://hc.apache.org/httpcomponents-client-4.3.x/httpclient/examples/org/apache/http/examples/client/ClientCustomSSL.java

+0

我们如何在上述代码中允许连接到没有证书不安全的SSL站点? – 2016-01-07 12:17:19

+0

您使用的是哪个版本的HTTPClient? – 2016-01-07 12:52:03

+0

@ user4567570我认为是4.3.5。要不安全地连接,你需要允许Hostname Verifier允许所有,但你还需要指定使用一种信任每个人的策略:'sslContextBuilder.loadTrustMaterial(new TrustAllStrategy());''和'TrustAllStrategy'实现'TrustStrategy',它只是'返回true;' – EpicPandaForce 2016-01-07 12:58:51

相关问题