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
Activity Node Excludes Previous Approvers Without Exclusion Settings in RSA Governance & Lifecycle 3Number of Views Role attributes are updated in wrong fields when creating or editing a role with separators in RSA Governance & Lifecycle 2Number of Views Migration to version 7.5.2 P03 or later completes with ORA-31011: XML parsing failed error in RSA Governance and Lifecycle 150Number of Views Create Account fails if previous Create Account is pending in RSA Identity Governance & Lifecycle 99Number of Views RSA Identity Governance & Lifecycle Access Fulfillment Express (AFX) Change Requests that depend on Entitlements Require A… 409Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?