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 Number of Views How user-entitlement clusters works when Role Mining in RSA Identity Governance & Lifecycle Number of Views Timeout when editing a collector in RSA Governance & 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 The display sequence of custom User Attribute Separators is incorrectly and unpredictably modified after making edits to U… Number of Views
Trending Articles
RSA Announces the Release of RSA MFA Agent 2.5 for Microsoft Windows RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to generate a PASSCODE for manual entry on a Ericsson R380 WAP phone
Don't see what you're looking for?
