User Are Unable To Login After Default Install And Configuration Of Secure Global Desktop Gateway
(Doc ID 1607720.1)
Last updated on JUNE 18, 2019
Applies to:Oracle Secure Global Desktop - Version 5.1 and later
Information in this document applies to any platform.
After the default installation and configuration of Oracle Secure Global Desktop (SGD) 5.1 Gateway, there is no access to the system via the Gateway. Users do not get a chance to enter their credentials.
Direct access to the SGD server works but connecting via the Gateway gives the error:
Proxy Error, Reason: Error during SSL handshake with remote server
in the browser window.
In /opt/SUNWsgsd/proxy/var/log/proxy.log these messages can be seen:
at async.channel.ssl.filter.AsyncSSLFilterChannelService$ReadHeaderOp.parseBuffer(Unknown Source)
at async.channel.util.AsyncTimeoutReadOp.onReadComplete(Unknown Source)
at async.channel.util.AsyncTimeoutReadOp$1.run(Unknown Source)
[Tue Dec 03 22:51:26 2013] [error] (502)Unknown error 502: proxy: pass request body failed to <IP ADD>:443 (<DOMAINNAME>)
[Tue Dec 03 22:51:26 2013] [error] [client 127.0.0.1] proxy: Error during SSL Handshake with remote server returned by /sgd/
[Tue Dec 03 22:51:26 2013] [error] proxy: pass request body failed to <IP ADD>:443 (<DOMAINNAME>) from 127.0.0.1 ()
<IP ADD> - - [03/Dec/2013:22:51:17 +0100] "-" 408 -
<IP ADD> - - [03/Dec/2013:22:51:26 +0100] "-" 408 -
None, with the possible exception of firewall rules between the open internet and the gateway server.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document