Understanding Secure Global Desktop Java Client Archive Signing
(Doc ID 2328375.1)
Last updated on JANUARY 22, 2020
Oracle Secure Global Desktop Information in this document applies to any platform.
Users connecting to an Oracle Secure Global Desktop (SGD) server may be prompted to download and install SGD a SGD client to enable full featured emulation of provisioned applications. Depending on the version, and configuration of the SGD server, one of the options that may be offered is the use of legacy Java Client.
Additional details regarding available modalities--and important changes on how these are made available to connecting users can be found within the following document:
(Doc ID 2380456.1) - Using the Client Options Menu to Select Client Types in Secure Global Desktop
SGD's Java Client archives are signed using a public signing certificate managed by Oracle Software Engineering to assure the connecting user of both the content and origin of the software contained within the signed archive. This document is intended to provide details specific to the archive-signing process for these archives, as well as to serve as an index for any alerts related to this functionality.
Please note: The statements in this document are specific to the certificate used to sign the legacy Java client archives as an authentic Oracle software product. This is fundamentally different than the site-specific security certificates a SGD Administrator may install to assure their users that they are connecting to a unique SGD deployment.
For more details on these differences, as well as how security certificates are used by Secure Global Desktop, please see the following resources within the published product documentation.