Last updated on JULY 17, 2017
Applies to:Oracle Secure Global Desktop - Version 4.6 to 5.3 [Release 4.0 to 5.0]
Information in this document applies to any platform.
End users may report that attempts to login to Oracle Secure Global Desktop (SGD) may not complete, often hanging on a "Loading..." message after submitting authentication credentials.
There are three prerequisites to the behavior that is described in this knowledge article. Any of the following changes may lead to this behavior in a previously working production environment include:
- The Java plug-in installed at the connecting client may have been upgraded from Java 1.6 to Java 1.7.
Note: This can happen without user intervention or action if Java updates are configured to be automatic.
- It is also possible that the URL used to connect to the SGD servers has been changed so that it no longer matches the ServerName parameter within the VirtualHost section defined in the SGD-supplied Apache configuration file.
In a standard SGD 4.7 installation, this file may be found at: /opt/tarantella/webserver/apache/2.2.22_openssl-1.0.0j_jk1.2.37/conf/httpd.conf )
- Or, the types of connections used between clients and SGD servers may have changed from standard to secure.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms