Action Required Service Updates

API Replacement: Secure Gateway Service for IBM Cloud

Share this post:

The Secure Gateway Service team is making changes to further improve security and to prepare for the EU General Data Protection Regulation (GDPR).

Are you using the SDK or API to create destinations? 

  • You’ll need to download the new SDK or call the new API and method by 6 May 2018
  • We always recommend using the most secure methods possible, but allow options for users to configure to fit their needs
  • This is a part of designing for security and the EU GDPR

Background:

As a part of this work we will be updating the Graphical User Interface (GUI), the Software Development Kit (SDK) and the Application Programming Interface (API) for creating a destination through the Secure Gateway Service. While the secure tunnel between the installable Secure Gateway Client and the Server in IBM Cloud is always secured with TLS, we offer the user the option to configure both connections on either side of the tunnel. That is: both the connection between the client and the destination/resource and the connection between the Server and user or application can be specified. We offer the option to use a variety of protocols and security methods including support of TLS, TCP, HTTPS, HTTP, and UDP.

Changes to SDK and API:

The updated Create Destination action for the management API will require a user to explicitly specify choices related to the protocol and security methods for a destination being created, there will no longer be a default for these. We have published and documented an updated SDK  that calls the updated API and requires the explicit user action to specify protocol and security methods which is available here. The new SDK and API will be available in all regions after 1AM EST on 7 March.  All users of the SDK should download and implement the updated SDK as soon as possible to take advantage of the improved security by design. Any users choosing to call the API directly should be sure to do so using the new path and methods as described in the SDK documentation linked above. The previous API and methods will be supported in private for 60 days until 6 May and then all users must call the new version. After this date calling the previous API will return an error.

For Your Information:

Users of the GUI will notice that the protocol and methods now default to the most secure option (TLS-MA).

We have also recently updated our mini-Service Description (mini-SD) to reflect both GDPR declarations regarding data protection and the name change of the IBM Cloud Platform, you can view the new terms in the mini-SD here.

Please Note:

Clients are responsible for ensuring their own compliance with various laws and regulations, including the European Union General Data Protection Regulation. Clients are solely responsible for obtaining advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulations that may affect the clients’ business and any actions the clients may need to take to comply with such laws and regulations.  The products, services, and other capabilities described herein are not suitable for all client situations and may have restricted availability. IBM does not provide legal, accounting or auditing advice or represent or warrant that its services or products will ensure that clients are in compliance with any law or regulation.

Learn more about IBM’s own GDPR readiness journey and our GDPR capabilities and offerings to support your compliance journey here.

 

As always, we’re here to help! Please reach out to us in the support forums.

More Action Required Service Updates stories

GDPR updates to IBM Analytics Engine

In consideration of GDPR regulations, IBM has made changes to the IBM Analytics Engine Cloud Service to provide improved security and compliance readiness, and needs you to take certain actions to include those changes as part of your applications. All customers are required to do this irrespective of their geography, or the type of data […]

Continue reading

Removal of Apache Kafka 0.9 Java client support from Message Hub

Message Hub is a fully supported Apache Kafka as a service offering available from IBM. As the open source community continues to evolve Apache Kafka, we bring these changes forward in the IBM Message Hub implementation as well. As a result, from the 31st of May, we will remove support for our custom JAR login […]

Continue reading

IBM Single Sign On for IBM Cloud Deprecation

As of April 30, 2018, the service tile will be removed from the IBM Cloud Public catalog and you will no longer be able to provision new instances. However, existing instances will continue to be supported. Also, after April 30, 2018, new customers will not be able to order IBM Single Sign On for IBM Cloud.

Continue reading