Skip to content

Latest commit

 

History

History
76 lines (49 loc) · 2.25 KB

securegateway_updates.md

File metadata and controls

76 lines (49 loc) · 2.25 KB
copyright lastupdated
years
2015, 2017
2017-04-25

{{site.data.keyword.SecureGateway}} Change Log

v1.7.0 Fixpack 1

Fixes

  • Fixes EADDRINUSE error caused by listeners not tearing down appropriately on destination deletion.
  • Resolves issue where service instances bound to an application could not be deleted.

v1.7.0

Features

  • Introduces new service plans: Essentials, Professional, and Enterprise.
  • The Secure Gateway Client now supports SOCKS proxy between itself and the on-prem destination.

v1.6.0 Fixpack 1

Fixes

  • Resolves issue where disconnecting multiple clients results in orphaned processes in the connected clients array.
  • Now cleans up orphaned connections that resulted in incorrecty paused listeners.

v1.6.0

Features

  • Access Control List now supports specific path routing for HTTP/S requests.
  • Destinations now support Server Name Indicators for TLS connections.

v1.5.1

Features

  • Destination wizard added for destination creation.
  • Gateways now support uploading a custom cert/key pair.
  • Services are now limited to 50 gateways and 50 destinations per gateway.
  • Destinations/Gateways/Services can now be exported/imported.
  • Latency tests between client and server capable of being executed from Secure Gateway UI.

v1.5.0 Fixpack 1

Fixes

  • Cleans up orphaned tunnel processes on network disconnect.
  • Resolves duplicate port allocation caused by failed destination deletion.
  • Resolves HTTP/S issue with non-UTF8 encoding.
  • Resolves missing IPC handlers on replacement processes.

v1.5.0

Features

  • Client now has a local interactive UI.
  • UDP connections are now supported.
  • Memory footprint of the client has been drastically reduced.
  • Single client mode is no longer supported; multi-client will be default and transparent to a single-gateway client.
  • Access Control List synchronizes between clients connected to the same gateway.

v1.4.2

Features

  • Clients are now assigned an ID when connecting to the SG server.
  • Clients an now be terminated remotely via API or the Secure Gateway UI.
  • The connected status of a client can be checked via API.
  • Destination-side TLS now supports Mutual Authentication.
  • Cloud destinations now support Mutual Authentication protocols.