What is Schema.Mitigator.pruneAttributes in SilverTail v4.x
Originally Published: 2013-06-24
Article Number
Applies To
Issue
Resolution
This caused Mitigator memory usage to appear unbounded and can easily exceeded available physical memory.
To mitigate this, a new feature pruneAttributes was introduced.
The decision to determine which attributes to add to this setting can be based on the following set of guidelines.
In general:
a) You cannot prune attributes that are used in schema.keys or used in mitigator rules (in the rule itself or in the incident details).
b) You cannot prune attributes if other required attributes depend on it.
c) Default attributes like guid-out, next-guid, prev-guid-out and user attributes used in login page definitions (like: user-from-login) can be prune
Related Articles
Unable to edit Role Membership Rule in RSA Governance & Lifecycle 35Number of Views Timeout when editing a collector in RSA Governance & Lifecycle 148Number of Views Role attributes are updated in wrong fields when creating or editing a role with separators in RSA Governance & Lifecycle 9Number of Views Membership Rule Or Entitlement Rule under Roles show the Display Description and full code condition for Role Set in RSA G… 2Number of Views Previously configured email alerts are no longer triggering in RSA Web Threat Detection 27Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service LDAP password authentication failed - Logon failure: unknown username or invalid password when attempting RADIUS authentic…
Don't see what you're looking for?