com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

Atlassian JIRA | Carlen Benard | 1 year ago
  1. 0

    [BAM-16239] Bamboo should support the use of TLS - SNI - Atlassian JIRA

    atlassian.com | 1 year ago
    com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
  2. 0

    h2. Description When creating AppLinks between Bamboo and another Atlassian application going through a proxy set up with SNI, the AppLinks won't work properly. This issue is caused by the commons-httpclient version (3.0.1) used by Bamboo, which does not have support for TLS - SNI. h3. Environment Java version 1.7 or newer (starting from the java version 1.7 TLS 1.1 and 1.2 are disabled by default). h3. Expected results The AppLink can be successfully created. h3. Actual results It is not possible to successfully create an AppLink and the following stack trace can be found in the {{atlassian-bamboo.log}} {noformat} 2015-09-01 17:02:29,222 ERROR [http-bio-8085-exec-11] [CreateApplicationLinkUIResource] ManifestNotFoundException thrown while retrieving manifest com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:201) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(AppLinksManifestDownloader.java:44) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(AppLinksManifestDownloader.java:86) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:79) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:76) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) ... ... {noformat} h3. Notes {panel} (i) This ticket is about the link from Bamboo to another Atlassian application. The improvement related to the connection from JIRA to Bamboo (or any other Atlassian applications) is described here JRA-24515. {panel} h3. Workarounds {panel} (i) As this issue is fixed, please consider upgrading before applying any of the following workarounds. {panel} The following workaround options are alternatives, please choose the best one for your case. +Workaround - option #1+ Use a newer {{commons-httpclient}} jar version (you need at least version {{3.1-atlassian-2}}) by following these steps: # # Shutdown Bamboo # Download this [commons-httpclient-3.1-atlassian-2.jar|https://maven.atlassian.com/content/repositories/atlassian-3rdparty/commons-httpclient/commons-httpclient/3.1-atlassian-2/commons-httpclient-3.1-atlassian-2.jar] into the machine hosting Bamboo # Backup and delete {{/opt/atlassian/bamboo/atlassian-bamboo/WEB-INF/lib/commons-httpclient-3.0.1.jar}} # Move the file {{commons-httpclient-3.1-atlassian-2.jar}} into the directory {{/opt/atlassian/bamboo/atlassian-bamboo/WEB-INF/lib}} # Restart Bamboo +Workaround - option #2+ Add the following Java properties to the [Bamboo Java properties|https://confluence.atlassian.com/bamboo/configuring-bamboo-on-start-up-289277345.html]: {code} -Dhttps.protocols=TLSv1.1,TLSv1.2 {code} +Workaround - option #3+ Connect the Atlassian applications bypassing the proxy. You can find the instructions describing the changes required to your environment, and how to recreate the AppLinks bypassing the proxy here: [How to create an unproxied Application Link|https://confluence.atlassian.com/display/KB/How+to+create+an+unproxied+Application+Link]

    Atlassian JIRA | 1 year ago | Turner Benard [Atlassian]
    com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
  3. 0

    h2. Description When creating AppLinks between FishEye/Crucible and another Atlassian application behind a reverse proxy set up with SNI, the AppLinks won't work properly. Because the client does not support SNI, it won't be served the right SSL certificate and the connection will failed. This issue is caused by the commons-httpclient version (3.1) used by FishEye/Crucible, which does not have support for TLS - SNI. h3. Environment Java version 1.7 or newer (starting from the java version 1.7 TLS 1.1 and 1.2 are disabled by default). h3. Expected results The AppLink can be successfully created. h3. Actual results It is not possible to successfully create an AppLink and the following stack trace can be found in the {{atlassian-fisheye-YYYY-MM-DD.log}} {noformat} 2015-09-01 17:02:29,222 ERROR [http-bio-8085-exec-11] [CreateApplicationLinkUIResource] ManifestNotFoundException thrown while retrieving manifest com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:201) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(AppLinksManifestDownloader.java:44) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(AppLinksManifestDownloader.java:86) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:79) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:76) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) ... ... {noformat} h3. Notes {panel} (i) This ticket is about the link from FishEye/Crucible to another Atlassian application. The improvement related to the connection from JIRA to FishEye/Crucible (or any other Atlassian applications) is described here JRA-24515. The improvement related to the connection from Bamboo to any other Atlassian applications is described here BAM-16239. {panel} h3. Workarounds {panel} (i) As this issue is fixed, please consider upgrading before applying any of the following workarounds. {panel} The following workaround options are alternatives, please choose the best one for your case. +Workaround - option #1+ Use a newer {{commons-httpclient}} jar version (you need at least version {{3.1-atlassian-2}}) by following these steps: # Shutdown FishEye/Crucible # Download this [commons-httpclient-3.1-atlassian-2.jar|https://maven.atlassian.com/content/repositories/atlassian-3rdparty/commons-httpclient/commons-httpclient/3.1-atlassian-2/commons-httpclient-3.1-atlassian-2.jar] into the machine hosting FishEye/Crucible # Backup and delete {{<FISHEYE_DIR>/lib/commons-httpclient-3.1.jar}} # Move the file {{commons-httpclient-3.1-atlassian-2.jar}} into the directory {{<FISHEYE_DIR>/lib}} # Restart FishEye/Crucible +Workaround - option #2+ Add the following Java properties to the [FishEye/Crucible JVM properties|https://confluence.atlassian.com/fisheye/environment-variables-298976934.html]: {code} -Dhttps.protocols=TLSv1.1,TLSv1.2 {code} +Workaround - option #3+ Connect the Atlassian applications bypassing the proxy. You can find the instructions describing the changes required to your environment, and how to recreate the AppLinks bypassing the proxy here: [How to create an unproxied Application Link|https://confluence.atlassian.com/display/KB/How+to+create+an+unproxied+Application+Link]

    Atlassian JIRA | 1 year ago | Caterina Curti [Atlassian]
    com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    h2. Description When creating AppLinks between Bamboo and another Atlassian application going through a proxy set up with SNI, the AppLinks won't work properly. This issue is caused by the commons-httpclient version (3.0.1) used by Bamboo, which does not have support for TLS - SNI. h3. Environment Java version 1.7 or newer (starting from the java version 1.7 TLS 1.1 and 1.2 are disabled by default). h3. Expected results The AppLink can be successfully created. h3. Actual results It is not possible to successfully create an AppLink and the following stack trace can be found in the {{atlassian-bamboo.log}} {noformat} 2015-09-01 17:02:29,222 ERROR [http-bio-8085-exec-11] [CreateApplicationLinkUIResource] ManifestNotFoundException thrown while retrieving manifest com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:201) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(AppLinksManifestDownloader.java:44) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(AppLinksManifestDownloader.java:86) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:79) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:76) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) ... ... {noformat} h3. Notes {panel} (i) This ticket is about the link from Bamboo to another Atlassian application. The improvement related to the connection from JIRA to Bamboo (or any other Atlassian applications) is described here JRA-24515. {panel} h3. Workarounds {panel} (i) As this issue is fixed, please consider upgrading before applying any of the following workarounds. {panel} The following workaround options are alternatives, please choose the best one for your case. +Workaround - option #1+ Use a newer {{commons-httpclient}} jar version (you need at least version {{3.1-atlassian-2}}) by following these steps: # # Shutdown Bamboo # Download this [commons-httpclient-3.1-atlassian-2.jar|https://maven.atlassian.com/content/repositories/atlassian-3rdparty/commons-httpclient/commons-httpclient/3.1-atlassian-2/commons-httpclient-3.1-atlassian-2.jar] into the machine hosting Bamboo # Backup and delete {{/opt/atlassian/bamboo/atlassian-bamboo/WEB-INF/lib/commons-httpclient-3.0.1.jar}} # Move the file {{commons-httpclient-3.1-atlassian-2.jar}} into the directory {{/opt/atlassian/bamboo/atlassian-bamboo/WEB-INF/lib}} # Restart Bamboo +Workaround - option #2+ Add the following Java properties to the [Bamboo Java properties|https://confluence.atlassian.com/bamboo/configuring-bamboo-on-start-up-289277345.html]: {code} -Dhttps.protocols=TLSv1.1,TLSv1.2 {code} +Workaround - option #3+ Connect the Atlassian applications bypassing the proxy. You can find the instructions describing the changes required to your environment, and how to recreate the AppLinks bypassing the proxy here: [How to create an unproxied Application Link|https://confluence.atlassian.com/display/KB/How+to+create+an+unproxied+Application+Link]

    Atlassian JIRA | 1 year ago | Carlen Benard
    com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
  6. 0

    h2. Description When creating AppLinks between FishEye/Crucible and another Atlassian application behind a reverse proxy set up with SNI, the AppLinks won't work properly. Because the client does not support SNI, it won't be served the right SSL certificate and the connection will failed. This issue is caused by the commons-httpclient version (3.1) used by FishEye/Crucible, which does not have support for TLS - SNI. h3. Environment Java version 1.7 or newer (starting from the java version 1.7 TLS 1.1 and 1.2 are disabled by default). h3. Expected results The AppLink can be successfully created. h3. Actual results It is not possible to successfully create an AppLink and the following stack trace can be found in the {{atlassian-fisheye-YYYY-MM-DD.log}} {noformat} 2015-09-01 17:02:29,222 ERROR [http-bio-8085-exec-11] [CreateApplicationLinkUIResource] ManifestNotFoundException thrown while retrieving manifest com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:201) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(AppLinksManifestDownloader.java:44) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(AppLinksManifestDownloader.java:86) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:79) at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:76) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) ... ... {noformat} h3. Notes {panel} (i) This ticket is about the link from FishEye/Crucible to another Atlassian application. The improvement related to the connection from JIRA to FishEye/Crucible (or any other Atlassian applications) is described here JRA-24515. The improvement related to the connection from Bamboo to any other Atlassian applications is described here BAM-16239. {panel} h3. Workarounds {panel} (i) As this issue is fixed, please consider upgrading before applying any of the following workarounds. {panel} The following workaround options are alternatives, please choose the best one for your case. +Workaround - option #1+ Use a newer {{commons-httpclient}} jar version (you need at least version {{3.1-atlassian-2}}) by following these steps: # Shutdown FishEye/Crucible # Download this [commons-httpclient-3.1-atlassian-2.jar|https://maven.atlassian.com/content/repositories/atlassian-3rdparty/commons-httpclient/commons-httpclient/3.1-atlassian-2/commons-httpclient-3.1-atlassian-2.jar] into the machine hosting FishEye/Crucible # Backup and delete {{<FISHEYE_DIR>/lib/commons-httpclient-3.1.jar}} # Move the file {{commons-httpclient-3.1-atlassian-2.jar}} into the directory {{<FISHEYE_DIR>/lib}} # Restart FishEye/Crucible +Workaround - option #2+ Add the following Java properties to the [FishEye/Crucible JVM properties|https://confluence.atlassian.com/fisheye/environment-variables-298976934.html]: {code} -Dhttps.protocols=TLSv1.1,TLSv1.2 {code} +Workaround - option #3+ Connect the Atlassian applications bypassing the proxy. You can find the instructions describing the changes required to your environment, and how to recreate the AppLinks bypassing the proxy here: [How to create an unproxied Application Link|https://confluence.atlassian.com/display/KB/How+to+create+an+unproxied+Application+Link]

    Atlassian JIRA | 1 year ago | Caterina Curti [Atlassian]
    com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.applinks.spi.manifest.ManifestNotFoundException

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

      at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1()
    2. com.atlassian.applinks
      AppLinksManifestDownloader$1.apply
      1. com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:201)
      2. com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(AppLinksManifestDownloader.java:44)
      3. com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(AppLinksManifestDownloader.java:86)
      4. com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:79)
      5. com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:76)
      5 frames
    3. Guava
      ComputingConcurrentHashMap$ComputingSegment.compute
      1. com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355)
      2. com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184)
      2 frames