|Applies To||RSA ClearTrust 5.5.3|
RSA ClearTrust 5.5.2
|Issue||Default cleartrust.eserver.cache.enabled in RSA ClearTrust 5.5.3|
By default, in RSA ClearTrust 5.5.3 Entitlements Server (EServer) cache is enabled. Performance improvements have been made to the Entitlements Manager (Admin GUI) and the underlying Administrative API. Some of the operations affected include:
- Searching for users
- Creating, modifying, and deleting users
- Listing users in a group
- Adding and removing users from groups
- Adding an administrative user to a role
The performance benefit of this release over previous versions increases with the size of the RSA ClearTrust installation in terms of the number of users, groups, users per group, and so on.
NOTE: Generally, when searching for data in the GUI, you should enter search criteria that will sufficiently limit your search results. If the result set is very large, the benefits of this hot fix may be limited.
If multiple RSA ClearTrust Entitlements Servers (EServers) are configured for failover, changes in one EServer do not show up immediately on the other EServers
|Cause||RSA ClearTrust hot fix 18.104.22.168 introduced new functionality in the form of a cache for the Entitlements Server (EServer). The default value for the cache in ClearTrust 5.5.2 was disabled. In ClearTrust 5.5.3, the default value for the EServer cache is enabled.|
|Resolution||If you do not desire to leverage the RSA ClearTrust Entitlements Server (EServer) cache function, ensure you have explicitly set the cleartrust.eserver.cache.enabled parameter to false:|
# Specifies whether the Entitlements Server will use caching. In some
# environments caching can improve the performance of the Entitlements Server.
# When multiple Entitlements Servers are deployed, their caches will not be
# Allowed Values:
# true or false
# Default Value:
|Workaround||Upgraded to RSA ClearTrust 5.5.3.x from version 5.5.2|
|Legacy Article ID||a24643|