Passwords are Not Cached Properly for Application Objects Configured with Application Server Groups within Oracle Secure Global Desktop
Last updated on OCTOBER 26, 2015
Applies to:Oracle Secure Global Desktop - Version 5.1 to 5.2 [Release 5.0]
Information in this document applies to any platform.
Secure Global Desktop Administrators may receive reports from users that passwords are not caching properly for application objects hosted by application server groups.
In this scenario, an application object that is configured to launch against a group of application servers may create a passcache entry to only the first member in that application server group. Subsequent launches that are directed to alternate application servers in the group may re-prompt for a password.
An example of the attributes for a group of application servers, configured within Secure Global Desktop:
With the above configuration, a launch of the application that is balanced to "salt" as the application server will successfully generate (or lookup) a passcache entry. Meanwhile, a launch of the same application that is directed to "pepper" will not successfully create (or match) a passcache record.
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