Details
-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
None
Description
In general it would be a useful way to allow users to "configure grouper" with the UI. ( It could be generalized much farther than just this use case. )
In particular the idea of identifying attributesNames that should be excluded from the PIT data via assigning an attribute (with values) to the attributeDef to exclude some or all the attributeNames from the PIT data. ( Basically move the config from grouper property files and into attribute values in Grouper. )
Something like:
:etc:attribute:PIT:excludeAttributeValues
Assignable to attributeDef's
Value = string
multi-valued
Each value would be the name of an attribute name ( or maybe support a "special value" of "*" for all?) to NOT log values in the PIT attribute values.
Other grouper settings could also be modeled this way as well. To make the config "editable" and "attributable" via permissions to objects in the UI.