PI42320: HOW TO FORCE THE ADAPTER TO USE TLSV1.1 WHEN MAKING HTTPS CONNECTIONS TO THE REMOTE SERVICE

IBM MobileFirst Platform Foundation Interim Fix README for 7.0
IBM MobileFirst Platform Foundation Interim Fix README for 6.3
IBM Worklight Interim Fix README for 6.2.0.1

APAR status

• Closed as new function.

Error description

• In the current API, it is not possible to force the adapter to
  use TLSv1.1 when making HTTPS connections to the remote service.
  As a result, calling WL.Server.invokeHttp(input) will fail when
  the remote service only use TLSv1.1 for its HTTPS traffic.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * HTTP adapters                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The HTTP adapters is not able to invoke services running in  *
  * a WebSphere Application Server where only TLS V1.1 or TLS    *
  * V1.2 are supported. The adapter uses always TLS V1.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• The fixe leverages the WebSphere Application Server SSL
  configuration to create the SSL context for the HTTP invocation.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WL/MFPF ENTERPR

• Fixed component ID

  5725I4300

Applicable component levels

• R620 PSY

     UP

• R630 PSY

     UP

• R700 PSY

     UP