Last updated on SEPTEMBER 08, 2017
Applies to:Oracle Secure Global Desktop - Version 5.3 and later
Information in this document applies to any platform.
Shortly after rolling out a new production Secure Global Desktop deployment, the SGD Administrator received reports from experienced users that attempts to launch applications from their provisioned workspaces were unexpectedly prompting for authentication credentials at every launch attempt, despite configuration enabling the caching of passwords.
By default, SGD stores all user names and passwords within a password cache. The default caching behavior is controlled by the System Default Password Cache level attribute. Users may be able to override this default behavior by setting their own password preferences, within the Password Preferences tab on their workspace. This functionality is explained within the Password Preferences section of the User Guide.
Reciprocally, details regarding the SGD server's common password management policy can be found within the Application Authentication section of the Administration Guide.
While researching this issue, the SGD Administrator found that even the SGD credentials (login, username) were not being automatically passed to the selected application server upon launch attempt, as expected in a default SGD deployment.
In this scenario, the SGD Administrator had recently begun testing with the "Login, Multiple" functionality for the Unix User Profile, a default profile shared by many users in the new production deployment.
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