【问题标题】:Mule - java.security.cert.CertificateException: No subject alternative names presentMule - java.security.cert.CertificateException:不存在主题替代名称
【发布时间】:2016-03-23 11:07:43
【问题描述】:

我需要向流发送 HTTPS 请求。为此,在调用流程中,我有一个 HTTPS 出站端点。其中的配置如下所示:

 <http:request-config name="HTTPS_Request_to_OnPrem"  host="0.0.0.0"  doc:name="HTTP Request Configuration" port="8083"  responseTimeout="30000" protocol="HTTPS">

</http:request-config>

现在暴露 HTTPS 的另一个流程如下所示:

<http:listener-config name="HTTPS_Domain"  host="0.0.0.0" port="8083" doc:name="HTTP Listener Configuration" protocol="HTTPS">
    <tls:context>
        <tls:key-store type="jks" path="keystore" keyPassword="*****" password="*****"/>
    </tls:context>

</http:listener-config> 

在运行并点击请求时,我的应用程序失败并出现以下错误:

********************************************************************************
Message               : Error sending HTTP request. Message payload is of   type: String
Type                  : org.mule.api.MessagingException
Code                  : MULE_ERROR--2
Payload               : some payload 
JavaDoc               :     http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html

Exception stack is:
1. No subject alternative names present    (java.security.cert.CertificateException)
  sun.security.util.HostnameChecker:142 (null)
2. General SSLEngine problem (javax.net.ssl.SSLHandshakeException)
  sun.security.ssl.Alerts:192    (http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/net/ssl/SSLHandshakeExceptio    n.html)
3. General SSLEngine problem (javax.net.ssl.SSLHandshakeException)
  sun.security.ssl.Handshaker:1336    (http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/net/ssl/SSLHandshakeExceptio    n.html)
4. javax.net.ssl.SSLHandshakeException: General SSLEngine problem     (java.util.concurrent.ExecutionException)
  org.glassfish.grizzly.impl.SafeFutureImpl$Sync:349 (null)
5. java.util.concurrent.ExecutionException:   javax.net.ssl.SSLHandshakeException: General SSLEngine problem     (java.io.IOException)
  org.mule.module.http.internal.request.grizzly.GrizzlyHttpClient:234 (null)
6. Error sending HTTP request. Message payload is of type: String    (org.mule.api.MessagingException)
  org.mule.module.http.internal.request.DefaultHttpRequester:287    (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingExcepti    on.html)
********************************************************************************
Root Exception stack trace:
java.security.cert.CertificateException: No subject alternative names present
at sun.security.util.HostnameChecker.matchIP(HostnameChecker.java:142)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:91)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:347)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:255)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:138)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1433)
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:841)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:839)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1273)
at org.glassfish.grizzly.ssl.SSLUtils.executeDelegatedTask(SSLUtils.java:247)
at org.glassfish.grizzly.ssl.SSLBaseFilter.doHandshakeStep(SSLBaseFilter.java:669)
at org.glassfish.grizzly.ssl.SSLFilter.doHandshakeStep(SSLFilter.java:330)
at org.glassfish.grizzly.ssl.SSLBaseFilter.doHandshakeStep(SSLBaseFilter.java:583)
at org.glassfish.grizzly.ssl.SSLBaseFilter.handleRead(SSLBaseFilter.java:304)
at com.ning.http.client.providers.grizzly.SwitchingSSLFilter.handleRead(SwitchingSSLFilter.java:74)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:283)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:200)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:132)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:111)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:536)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112)
at org.mule.module.http.internal.request.grizzly.FlowWorkManagerIOStrategy.run0(FlowWorkManagerIOStrategy.java:134)
at org.mule.module.http.internal.request.grizzly.FlowWorkManagerIOStrategy.access$100(FlowWorkManagerIOStrategy.java:31)
at org.mule.module.http.internal.request.grizzly.FlowWorkManagerIOStrategy$WorkerThreadRunnable.run(FlowWorkManagerIOStrategy.java:157)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:591)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:571)
at java.lang.Thread.run(Thread.java:745)

【问题讨论】:

    标签: ssl mule


    【解决方案1】:

    您正在向 0.0.0.0 发送 HTTPS 请求,而您在那里运行的证书并未将 0.0.0.0 列为 SAN

    您应该:

    • 更改请求 host 以匹配您证书中的内容,
    • 在证书中为 0.0.0.0 添加 SAN。

    【讨论】:

      猜你喜欢
      • 2014-04-02
      • 1970-01-01
      • 2020-08-12
      • 1970-01-01
      • 2020-07-08
      • 2014-04-25
      • 2023-04-11
      • 2019-05-09
      • 1970-01-01
      相关资源
      最近更新 更多