Forum Discussion
Stan_Ward
Altocumulus
AltocumulusHow can non-custom APM session variables be secured?
When reading data from LDAP, we have data other than passwords that is sensitive. The sensitive data can be moved to a [S] secure custom variable; however, the original values are unsecure and still can appear in APM logs, reports, etc.
How can APM session variables that are not custom (such as session.ldap.last.attrib.XXX) be made secure, similar to user entered passwords from a login box?
Stanislas_Piro2Cumulonimbus
You can use a variable assign
session.ldap.last.attrib.XXX Secure expr {[mcget {session.ldap.last.attrib.XXX}]}