Previous Topic: Issues Fixed in CA EEM r8.4 SP3Next Topic: Issues Fixed in CA EEM r8.4 SR01


Issues Fixed in CA EEM r8.4 SR02

The following STAR issues are fixed in this release:

STAR Issue Number

Description of the STAR Issue

16654975

iGateway memory usage growth increases due to memory defragmentation used by Windows.

16843262

Policies that include /* in the resources field are not displayed in the GUI.

17605187

When retrieving users, if user first and last names have special characters such as '&', '<', '>', and so on, CA EEM Java SDK changes these special characters to their escape sequences.

17729293

When you create a policy of policy type, Identity Access Control List, CA EEM lets you assign different permissions to the same user.

18100525

Cannot login to applications that are protected by CA EEM if any of the CA EEM Servers in the failover setup are not available.

18100943

In a failover setup, when the CA EEM Server 1 is down, any policy changes you make in the replicated servers are saved, but the confirmation message is not displayed.

18119830

When you logout from CA EEM, CA EEM crashes.

18122029

CA EEM inserts an ampersand '&' to object search filters if AllUsersFilter is not used. This insertion increases the processing cycles to the LDAP server.

18167627

The maximum size of App Objects in CA EEM is only 2.5 MB.

18181773

The searchMatchingPoliciesByResource API in Java SDK does not accept '*' as input; so, the Java SDK performance is affected.

18205860

log4cxx messages that are displayed when registering or unregistering applications through safex must be recorded with relevant log messages in the log file.

18246763

When iGateway starts, it creates a defunct process.

18250914

CA EEM installation fails on a machine german language version of Windows.

18261887

During policy evaluation, CA EEM treats global users user name, application users name, global and application groups as case sensitive.

18318532

CA EEM inserts an ampersand '&' in filters in LDAP queries. This insertion increases the processing cycles to the LDAP server.

18320089

Some resource filters are not saved properly if the regular expressions for resources contain an escape character '\'.

18358337

When the primary CA EEM Server recovers in a failover setup, applications protected by CA EEM have to be restarted to authenticate users.

18360263

CA EEM lets logged-in users to view home page in a different session without logging in.

18434870

In a CA EEM failover setup, application registration information is not replicated from the primary server to the secondary servers.

18443918

The version of log4j shipped with SAML must be the same as the version being used by Java SDK.

18451973

CA EEM SDK hangs when you use the Safe::Cache::Stop call.