why failed to create appslink even after change the ssl protocol
Asked by Norhanizawati Zainol Zainoon:

hi,

we been trying to add a jira link but it keep on having same error below

aused by: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)  
at sun.security.ssl.Handshaker.activate(Handshaker.java:438)  
at sun.security.ssl.SSLSocketImpl.kickstartHandshake(SSLSocketImpl.java:1426)  
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1296)  
at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:698)  
at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:119)  
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)  
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)  
at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:828)  
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2116)  
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)  
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)  
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)  
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)  
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)  
at com.atlassian.sal.core.net.HttpClientRequest.executeMethod(HttpClientRequest.java:596)  
at com.atlassian.sal.core.net.HttpClientRequest.executeMethod(HttpClientRequest.java:546)  
at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:350)  
at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161)  
at com.atlassian.plugins.rest.module.jersey.JerseyRequest.execute(JerseyRequest.java:141)  
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:150)  
... 220 more

we have tried to change the protocol but end up with the same error too.


Answers:
author: JP _AC Bielefeld Leader_
body: Hi,

I guess it's not a certificate problem in the first place. The protocol (https) and/or ssl configuration in server.xml seems to be wrong.

Getting SSL right within Confluence (to be precise: The Apache Tomcat application server) can be tricky, as you have to configure the Java certificate store. The first line of the error says it all:

javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

Consider using an Apache HTTPD server working as a reverse proxy in front of the Confluence server. We use this configuration to have single HTTPD server acting as a proxy to all Atlassian servers in our company: Confluence, Jira, Bitbucket,...

Easy to configure, only one place for SSL termination, secure setup.

Best

JP

comments: author: Norhanizawati Zainol Zainoon
body: yes. it works! thanks a lot. so jira change backed their protocol and make both confluence and jira protocol and all works fine. thanks again.


author: Mayur Supare
body: Hello ,

You need to share the certificate with both application

so that they can communicate with each other

Thanks,

Mayur


Tags: confluence-server

server