RRDI for CLM - HTTPS question
Hi,
we've integrated RRDI with our CLM installation. Everything is working fine, except now we want to use HTTPS to access RRDI (RRDI is using HTTP by default). We've found some instructions of how to do that here: http://publib.boulder.ibm.com/infocenter/c8bi/v8r4m0/index.jsp?topic=/com.ibm.swg.im.cognos.inst_cr_winux.8.4.0.doc/inst_cr_winux_id18006ConfigureSSLforCognos8.html When we configure HTTPS as described above we can't access RRDI anymore (we get a web page saying that RRDI is still initializing). There is an error in the SystemOut.log: at com.ibm.jsse2.gb.t(gb.java:174) at com.ibm.jsse2.pc.b(pc.java:199) at com.ibm.jsse2.pc.c(pc.java:448) at com.ibm.jsse2.pc.wrap(pc.java:343) at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:37) at com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtils.java:732) at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInbound(SSLConnectionLink.java:562) at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.ready(SSLConnectionLink.java:291) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563) Caused by: javax.net.ssl.SSLHandshakeException: no cipher suites in common at com.ibm.jsse2.n.a(n.java:44) at com.ibm.jsse2.pc.a(pc.java:410) at com.ibm.jsse2.gb.a(gb.java:285) at com.ibm.jsse2.gb.a(gb.java:40) at com.ibm.jsse2.ib.a(ib.java:15) at com.ibm.jsse2.ib.a(ib.java:136) at com.ibm.jsse2.ib.a(ib.java:315) at com.ibm.jsse2.gb.n(gb.java:42) at com.ibm.jsse2.gb$0.run(gb$0.java:1) at java.security.AccessController.doPrivileged(AccessController.java:284) at com.ibm.jsse2.gb$b_.run(gb$b_.java:9) at com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtils.java:790) ... 12 more The certificate used has not expired and it is from the trusted source. We are using Windows Server 2008 64- bit. Our application server is WAS 7.0.0.19 32-bit. CLM version is 3.0.1.2 and RRDI version is 1.0.2.1. |
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.