IBM Support

MaaS360 Product Suite TLS v1.1 Deprecation Notice

News


Abstract

The IBM MaaS360 Product Suites will be deprecating support for TLS v1.1 on December 4, 2020. Please read the below information to test for any impacts.

Content

What is TLS?

The primary goal of the TLS (Transportation Layer Security) protocol is to provide privacy and data integrity between two communicating applications. The protocol is composed of two layers: TLS Record Protocol and TLS Handshake Protocol.  At the lowest level, layered on top of some reliable transport protocol (e.g., TCP), is the TLS Record Protocol.  It is the most widely deployed security protocol used today.  It is used for web browsers and other applications that require data to be securely exchanged over a network or internet. TLS ensures that a connection to a remote endpoint is the intended endpoint through encryption and endpoint identity verification. The versions of TLS available today are TLS 1.0, 1.1, 1.2, and 1.3. The MaaS360 Product Suite deprecated TLS 1.0 on June 25, 2018.   

How this relates to the MaaS360 Product Suite

On December 4, 2020, IBM MaaS360 will start deprecating support for TLS 1.1 and will disable encryption protocol across services. MaaS360 continues to support TLS 1.2 to align with the PCI security standards and ensure highest security and safety of your data. 
Below  provides details of the impact of this deprecation across the MaaS360 Product Suite.
MaaS360 Product Impact Action
iOS Apps, SDK and App Wrapping none none
Andriod Apps, SDK and App Wrapping none none
Windows Apps and Desktop Agents none
none
Cloud Extender and Enterprise Gateway none none
MaaS360 Platform WebServices possible See 'Testing TLS v1.2 Compatibility' section below
3rd Party Portal Integrations possible  See 'Testing TLS v1.2 Compatibility' section below
Testing TLS v 1.2 Compatibility 
For those customers using WebServices/API's or have enabled 3rd Party Integrations using API's on the MaaS360 Platform, the API client used on the Customer side may require adjustments or upgrades. Please check with your client's documentation for TLS 1.2 support.

Steps to check for API compatibility

  1. Set up an API client in a test environment. This could be any software or library that you are using to integrate to the MaaS360 Platform or any custom integration code that you have written. The examples cited in this write up uses python as a client language. This could be Java or any other language in your environment.
  2. A web service client usually makes GET and POST requests to servers.
  3. Using your client test environment, make a GET request to the following URL https://tlstest.maas360.com/.
  4. Your version of client library should be able to make a successful GET request to the URL above and receive a result of "0". This response means that underlying TLS v1.2 connection is successful.
  5. If you get anything other than "0" in the result, it would indicate that the client you have could not make a successful connection to our servers which has TLS v1.1 disabled. You need to upgrade your client library which supports TLS v1.2 and run the same test to confirm you are getting a result of "0". 

An example of doing this in a python script is as follows:
  import requests
  url = "https://tlstest.maas360.com/"
  data = requests.get(url)._content
  assert data == "0"

If you are using python for consuming MaaS360 web services then, run this code to see if your client connects to a URL that has TLS v1.1 disabled.

Note: If you are using a different programming language, you can write similar code in that environment language and verify using the test URL if the client works with the URL that has TLS v1.1 disabled.

[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSXX","label":"IBM MaaS360"},"ARM Category":[{"code":"a8m0z0000000712AAA","label":"INTEGRATIONS"},{"code":"a8m0z000000070eAAA","label":"SETUP"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
18 November 2020

UID

ibm16361797