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
Role attributes are updated in wrong fields when creating or editing a role with separators in RSA Governance & Lifecycle Number of Views Activity Node Excludes Previous Approvers Without Exclusion Settings in RSA Governance & Lifecycle Number of Views Migration to version 7.5.2 P03 or later completes with ORA-31011: XML parsing failed error in RSA Governance and Lifecycle Number of Views Create Account fails if previous Create Account is pending in RSA Identity Governance & Lifecycle Number of Views Approval activity throws a Request Could Not Be Handled error in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
