I've been finding the is-sensitive setting is insufficient in IDM - the
first attempt that I have at making things sensitive from the publisher
side, is the input transform. That's after the document appears in the
log at least once.

The perfect solution in my mind would be to be able to specify the
sensitive attributes in a driver's Filter and/or mapping rule, so that
the shim can be notified from the beginning which attributes are
sensitive, and suppress them from the beginning. Then it's up to the
developer to continue to disable the trace when working with those
specific attributes in policy, in the same manner the password is
handled.

Any thoughts? Any one know how to request new features for IDM? Is
that still bugzilla?


--
akynaston
------------------------------------------------------------------------
akynaston's Profile: http://forums.novell.com/member.php?userid=23027
View this thread: http://forums.novell.com/showthread.php?t=443803