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
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 Role attributes are updated in wrong fields when creating or editing a role with separators in RSA Governance & Lifecycle Number of Views RSA Access Manger error message 'This stream has been closed'. Number of Views Distribution of Software token with a binding DeviceSerialNumber may not be Case Sensitive Number of Views RSA Identify Governance and Lifecycle Password Challenge Questions "Challenge Responses" are case sensitive Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to replace the RSA Authentication Manager self signed console certificate with a signed certificate from Microsoft Act… RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to Request Access to the RSA Authentication Manager AMI for AWS via RSA Support
Don't see what you're looking for?
