Clients Can Not Connect to Secure Global Desktop Gateway After Application of JVM Update 1.8.0_51 (Doc ID 2036402.1)

Last updated on JANUARY 16, 2017

Applies to:

Oracle Secure Global Desktop - Version 5.1 to 5.2 [Release 5.0]
Information in this document applies to any platform.

Symptoms

Administrators of Oracle Secure Global Desktop (SGD) deployments may receive reports that clients are unable to connect to the SGD Gateway after application of the July 2015 JVM Update patch, 1.8.0_51.

In this scenario, connecting clients may appear to freeze at the client splash screen after authentication.  Users who have manually started the client may be presented with an error suggesting, "connection has been reset."   These symptoms are triggered when connections from the gateway are rejected by the ttassl process on the SGD server.

SGD Administrators may find errors logged in parallel with client connection failures, similar to the following:

TSP=192.168.10.10:5307 Client=192.168.100.7:52113
The client has established a TCP connection but failed to negotiate an SSL connection. Connection closed by Secure Global Desktop Security Daemon.
Reported SSL error: no shared cipher
Check the client supports SSL.
Web browsers must support JDK 1.1. ssldaemon/handshake/failederror

 

Changes

This unique condition may manifest only in the following deployment scenario:

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms