2016-11-14 81 views
0

我试图在我们正在构建的新Web服务上实现双向SSL,并且出现了一些问题。Tomcat - 双向SSL作为服务器

首先有关环境的一些信息。

Server version: Apache Tomcat/8.0.36 
Server built: Jun 9 2016 13:55:50 UTC 
Server number: 8.0.36.0 
OS Name:  Linux 
OS Version:  3.10.0-514.el7.x86_64 
Architecture: amd64 
JVM Version: 1.8.0_111-b14 
JVM Vendor:  Oracle Corporation 

我们使用内部证书颁发机构签署我们所有的证书。所以所有的客户端证书都由我们的内部根签名。当我信任客户端信任库中的根证书时,一切正常。所有由内部根工作签名的客户端证书。

但是,如果我从客户端信任存储库中删除根证书,并添加单个客户端证书,则会出现证书链错误。


*** ECDH ServerKeyExchange 
Signature Algorithm SHA512withRSA 
Server key: Sun EC public key, 256 bits 
    public x coord: 107108750176335210433834926983330116805775068919227166974389735341685270962458 
    public y coord: 93195725734236902743006469378087068209149058097948526490562555560744449337507 
    parameters: secp256r1 [NIST P-256, X9.62 prime256v1] (1.2.840.10045.3.1.7) 
*** CertificateRequest 
Cert Types: RSA, DSS, ECDSA 
Supported Signature Algorithms: SHA512withECDSA, SHA512withRSA, SHA384withECDSA, SHA384withRSA, SHA256withECDSA, SHA256withRSA, SHA256withDSA, SHA224withECDSA, SHA224withRSA, SHA224withDSA, SHA1withECDSA, SHA1withRSA, SHA1withDSA Cert Authorities: 
<CN=Client, OU=Information Technology, O=Company, L=Calgary, ST=Alberta, C=CA> 
*** ServerHelloDone 
http-nio2-8443-exec-4, WRITE: TLSv1.2 Handshake, length = 4482 http-nio2-8443-exec-2, READ: TLSv1.2 Handshake, length = 7 
*** Certificate chain 
<Empty> 
*** 
http-nio2-8443-exec-2, fatal error: 42: null cert chain 
javax.net.ssl.SSLHandshakeException: null cert chain %% Invalidated:[Session-2, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256] 
http-nio2-8443-exec-2, SEND TLSv1.2 ALERT: fatal, description = bad_certificate http-nio2-8443-exec-2, WRITE: TLSv1.2 Alert, length = 2 http-nio2-8443-exec-2, fatal: engine already closed. Rethrowing javax.net.ssl.SSLHandshakeException: null cert chain http-nio2-8443-exec-2, called closeOutbound() http-nio2-8443-exec-2, closeOutboundInternal() 

这对我们来说是一个问题,因为我们不能在公司的所有客户端证书授予访问这个端点,它那种失败的目的。

公司根证书位于服务器启动时使用的另一个信任存储区中。这是我的配置。

server.xml中的连接器:

<Connector protocol="org.apache.coyote.http11.Http11Nio2Protocol" 
      port="8443" maxThreads="24" minSpareThreads="4" maxSpareThreads="4" acceptCount="1000" server=" " 
      scheme="https" secure="true" SSLEnabled="true" 
      keystoreFile="certs/servercert.jks" keystorePass=" CrazyPasswordHere" 
      clientAuth="true" truststoreFile="/usr/local/tomcat/certs/clienttrust.jks" truststorePass="CrazyPasswordHere" 
      sslEnabledProtocols="TLSv1.2" sslProtocol="TLS" 
      ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, 
      TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,TLS_DHE_RSA_WITH_AES_128_CBC_SHA" 
      useServerCipherSuitesOrder="true" compression="on" compressionMinSize="2048" 
      compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript" /> 

Systemd初始化:

# Systemd unit file for tomcat 
[Unit] 
Description=Apache Tomcat 
After=syslog.target network.target 

[Service] 
Type=forking 

Environment=JAVA_HOME=/usr/lib/jvm/jre 
Environment=CATALINA_PID=/usr/local/tomcat/temp/tomcat.pid 
Environment=CATALINA_HOME=/usr/local/tomcat 
Environment=CATALINA_BASE=/usr/local/tomcat 
Environment='CATALINA_OPTS= -Xms2048M -Xmx2048M -server -XX:+UseParallelGC \ -Dcom.sun.management.jmxremote \ 
-Dcom.sun.management.jmxremote.port=8090 \ -Dcom.sun.management.jmxremote.ssl=false \ -Dcom.sun.management.jmxremote.authenticate=true \ -Dcom.sun.management.jmxremote.password.file=/usr/local/tomcat/conf/jmxremote.password \ -Dcom.sun.management.jmxremote.access.file=/usr/local/tomcat/conf/jmxremote.access \ -Djavax.net.debug=SSL \ -Djavax.net.ssl.trustStore=/usr/local/tomcat/certs/servertrust.jks \ -Djavax.net.ssl.trustStorePassword=CrazyPasswordHere \ -Djavax.net.ssl.keyStore=/usr/local/tomcat/certs/serverclient.jks \ -Djavax.net.ssl.keyStorePassword=CrazyPasswordHere ' 
Environment='JAVA_OPTS=-Djava.awt.headless=true -Djava.security.egd=file:/dev/./urandom' 

ExecStart=/usr/local/tomcat/bin/startup.sh 
ExecStop=/bin/kill -15 $MAINPID 

User=tomcat 
Group=tomcat 

[Install] 
WantedBy=multi-user.target 

这里任何投入将是巨大的!我无法想象这里的解决方案是每个由特定授权机构签署的客户证书应该有权访问...

谢谢!

回答

3

经典。您正在将认证与授权混为一谈。 SSL的工作是通过您已经设置的机制进行身份验证,以及您所说的正在完美工作。 Tomcat或应用程序的工作是使用该信息来定义谁有权使用该Web应用程序。这是通过web.xml,CMA等完成的。

+0

谢谢,你说得对。我不应该在我的连接字符串中启用clientauth,而是在我的web.xml中。我现在有这个设置并且很好地工作。 – user2735454