Technical data

Resolved Issues

Issues that were reported in earlier releases that have been resolved in this release include:

Tracking

Number Description of Issue

a8938 ESSO-LM deleted a Java applet’s Logon form control information when adding a Change Password

form with SendKeys to the template.

a9039 ESSO-LM did not accept credentials when using OpenLDAP 2.2.

a9090 ESSO-LM did not differentiate between SAP 6.20 Logon and Password Change screens.

a9164 ESSO-LM client did not respond to AppWorx password change screen due to a Java error.

a9317 ESSO-LM did not update Java support automatically to accommodate the current version.

a9322 Credential Sharing Groups functioned incorrectly for the username field.

a9377 ESSO-LM did not accept a URL value longer than 28 characters when creating a new entry through

the Client application.

a9394 Web Viewer did not display credentials beyond the first page.

a9401 The username text in the Web Viewer logon was difficult to read.

a9438 Templates imported into the console prior to password generation policies cleared the template’s

association with the policy.

a9446 Some Java applets locked up with ESSO-LM Java support installed.

a9451 ESSO-LM responded slowly to an SAP window when there were multiple templates configured with

field matching.

a9499 SAP behaved erratically when using SAP scripting and ESSO-LM.

a9502 The reference fields did not refresh to reflect current data in a template.

a9517 Web Viewer displayed lists incorrectly when switching view options.

a9541 Password change did not support combo boxes when configured in the logon template.

a9553 SSOBHO.exe caused the Add New Logon dialog prompt to loop infinitely when directed to a URL.

a9607 ESSO-LM caused a web browser to hang when directed to a URL.

a9653 ESSO-LM did not disable the shared fields when using shared groups. The fields were pre-filled but

still available for changing.

a9694 The MHO timer worked inconsistently, displaying the logon prompt at different intervals following a

“Not Now” response.

a9699 With the Startup/Shutdown event and CleanupOnShutdown enabled, ESSO-LM logging did not

record a shutdown event.

a9826 Launching a Java application from within an Internet Explorer window caused the system to hang

while SSObho.exe was running.

a9828/

a9890

When using COs, host or web applications in a Credential Sharing Group could not be brought back

to the Administrative Console.