EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

Using Community Connectors with an IBM WebSphere Application Server Produces the Error, "Received fatal alert: handshake_failure"


Jianglong Ma

Software Engineer, Principal • MicroStrategy


The article details how to resolve an handshake failure error that occurs when using Community Connectors with an IBM WebSphere application server.

Description

Using Community Connectors with an IBM WebSphere application server may produce the error, "Received fatal alert: handshake_failure." This happens when Community Connectors attempts to connect to an http source. This occurs with connectors that use OAuth authentication, such as Adobe Analytics, data.world, FitBit, Jira Cloud, Sharepoint, etc. In addition, this error is seen when using IBM JDK 7.x or 8.x with IBM WebSphere.
In the example shown below, the error appears after a user enters their credentials to log into Adobe Analytics. This is a result of Community Connectors requesting a token from the Adobe Analytics server thorough https. Other connectors may also produce this error if they are requesting an https source.

ka02R000000g4kqQAA_0EM2R000000ms5t.jpeg

Why is this happening?

A handshake failure is due to protocol registration failure between the application and target server.
There are three versions of security protocols for the transport layer of the network: TLSv1.0, TLSv1.1, and TLSv1.2. The recommended version for IETF protocols since 2008 is TLSv1.2.
Major browsers (Chrome, Firefox, Safari, Edge, and Internet Explorer 11) have stopped support for versions TLSv1.0 and TLSv1.1. However, the default protocol in IBM 7.x and 8.x is still TLSv1.0. This produces a handshake failure since version TLSv1.0 is no longer supported.

Solution

Use the following procedure to enable IBM WebSphere to use TLSv1.2.

  • Open the WebSphere Application Server Administration Console.
ka02R000000g4kqQAA_0EM2R000000ms7B.jpeg
  • Go to Servers > Server types > WebSphere application servers.
ka02R000000g4kqQAA_0EM2R000000ms7L.jpeg
  • Click the server name.
ka02R000000g4kqQAA_0EM2R000000ms7a.jpeg
  • Click Process definition.
ka02R000000g4kqQAA_0EM2R000000ms7k.jpeg
  • Click Java Virtual Machine.
ka02R000000g4kqQAA_0EM2R000000ms7z.jpeg
  • Add -Dcom.ibm.jsse2.overrideDefaultTLS=true to Generic JVM arguments.
ka02R000000g4kqQAA_0EM2R000000ms8d.jpeg
  • Click Save and restart the server.

See Matching the behavior of SSLContext.getInstance("TLS") to Oracle on the IBM Knowledge Center for more information.


Comment

0 comments

Details

Knowledge Article

Published:

November 21, 2019

Last Updated:

November 21, 2019