ssl - soap客户端无法通过启用SSL的saml身份验证访问Web服务

标签 ssl saml netbeans-7.3

我使用了=> http://metro.java.net/nonav/1.2/guide/Example_Applications.html#ahies中给出的示例
在带有jdk 7和glassfish 4.0的netbeans 7.3.1中尝试通过SSL进行saml身份验证。
但是,当我运行客户端代码时,出现异常

例外

javax.xml.ws.WebServiceException)javax.xml.ws.WebServiceException:无法通过以下网址访问WSDL:https://:8181 / CalculatorApplication / CalculatorWS?wsdl。它失败了:
    java.security.cert.CertificateException:找不到匹配的名称。

当我尝试创建服务时,JSP中出现了异常:

org.me.calculator.client.CalculatorWS_Service服务=新的org.me.calculator.client.CalculatorWS_Service();

尝试过此方法或遇到类似问题的任何人都可以帮助我吗?

完整的堆栈跟踪=>

严重:javax.xml.ws.WebServiceException:无法访问位于以下位置的WSDL:https://:8181 / CalculatorApplication / CalculatorWS?wsdl。它失败了:
    java.security.cert.CertificateException:找不到匹配的名称。
    在com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:249)
    在com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:230)
    在com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:193)
    在com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:162)
    在com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:359)
    在com.sun.xml.ws.client.WSServiceDelegate。(WSServiceDelegate.java:321)
    在com.sun.xml.ws.client.WSServiceDelegate。(WSServiceDelegate.java:230)
    在com.sun.xml.ws.client.WSServiceDelegate。(WSServiceDelegate.java:212)
    在com.sun.xml.ws.client.WSServiceDelegate。(WSServiceDelegate.java:208)
    在com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:112)
    在javax.xml.ws.Service。(Service.java:92)
    在org.me.calculator.client.CalculatorWS_Service。(CalculatorWS_Service.java:42)
    在org.apache.jsp.index_jsp._jspService(index_jsp.java:58)
    在org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
    在javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
    在org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:411)
    在org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
    在org.apache.jasper.servlet.JspServlet.service(JspServlet.java:377)
    在javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
    在org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682)
    在org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318)
    在org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160)
    在org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734)
    在org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673)
    在com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99)
    在org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174)
    在org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357)
    在org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260)
    在com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188)
    在org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191)
    在org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168)
    在org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189)
    在org.glassfish.grizzly.filterchain.ExecutorResolver $ 9.execute(ExecutorResolver.java:119)
    在org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288)
    在org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206)
    在org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136)
    在org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114)
    在org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
    在org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838)
    在org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113)
    在org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access $ 100(WorkerThreadIOStrategy.java:55)
    在org.glassfish.grizzly.strategies.WorkerThreadIOStrategy $ WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135)中
    在org.glassfish.grizzly.threadpool.AbstractThreadPool $ Worker.doWork(AbstractThreadPool.java:564)
    在org.glassfish.grizzly.threadpool.AbstractThreadPool $ Worker.run(AbstractThreadPool.java:544)
    在java.lang.Thread.run(Thread.java:724)
引起原因:javax.net.ssl.SSLHandshakeException:java.security.cert.CertificateException:找不到匹配的名称
    在sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
    在sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1884)
    在sun.security.ssl.Handshaker.fatalSE(Handshaker.java:276)
    在sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270)
    在sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341)
    在sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153)
    在sun.security.ssl.Handshaker.processLoop(Handshaker.java:868)
    在sun.security.ssl.Handshaker.process_record(Handshaker.java:804)
    在sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1016)
    在sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312)
    在sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)
    在sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1323)
    在sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
    在sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
    在sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1300)
    在sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
    在java.net.URL.openStream(URL.java:1037)
    在com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:983)
    在com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:384)
    在com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:215)
    ...另外44个
引起原因:java.security.cert.CertificateException:找不到匹配的名称
    在sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:208)
    在sun.security.util.HostnameChecker.match(HostnameChecker.java:93)
    在sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:347)
    在sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:203)
    在sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126)
    在sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1323)
    ...另外59个

最佳答案

这里有一个解决方案[1]。看起来这是一个已知问题。我没有尝试过他提出的解决方案,但看起来问题是在验证主机名。他正在覆盖验证方法。

       public boolean verify(String hostname,
                javax.net.ssl.SSLSession sslSession) {
            if (hostname.equals("localhost")) {
                return true;
            }
            return false;
        }


[1]-http://www.mkyong.com/webservices/jax-ws/java-security-cert-certificateexception-no-name-matching-localhost-found/

关于ssl - soap客户端无法通过启用SSL的saml身份验证访问Web服务,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/18739468/

相关文章:

java - 将 Office 365 与 ADFS 之外的基于 SAML 的自定义身份提供商集成

git - 网 bean 7.3 : Error connecting to Git repository with SSH

java - 在 Netbeans 7.3 中配置 Java HTTP servlet

python - 通过 torchvision 下载 pytorch 数据集时出现 SSLCertVerificationError

wordpress - ssl 在我的 wordpress 网站的 2 个页面中不起作用

node.js - 通过 Mongoose.js 使用 SSL 和 mongos 连接到 Compose.io MongoDB 部署

ssl - 访问 Nest api https ://developer-api. nest.com 导致 SSL 错误

windows - 使用 VBA 从具有 SAML 身份验证的网站下载文件

azure - SAML SSO 在 Websphere Liberty 中不起作用

netbeans - PHP-Netbeans : How to change formatting for multi-conditional if statements