The Object Model › Metadata Definition › How You Define Metadata for a New Connector › Handling Sensitive Data

Handling Sensitive Data

Among the many metadata properties which can be set for attributes, there are some you can use to protect sensitive data (for full documentation see com.ca.jcs.meta.MetaDataDefs in the Java CS Javadoc):

• isObfuscated – When set to true, the JCS uses an encryption algorithm to obfuscate incoming values for the target attribute (and de-obfuscate outgoing values in queries). An example obfuscated value is "{AES}xdrfa3567h", where the "{AES}" signifies the value was obfuscated using the AES algorithm.
• encryptAlgorithm – Can be used to specify an encryption algorithm to be used when isObfuscated=true ("AES" by default). The toString() values of the MetaDataDefs.EncryptAlgorithms enum define the available algorithms.
• dontPrefixAlgorithm – When set to true, this signifies that the attribute values won't be prefixed with the chosen algorithm.
• isEncrypted – When set to true, this signals to User Interface components that the value(s) for the attribute should be rendered as a password (that is, the characters are not echoed to the screen as they are typed).
• encryptWith – This setting can be used on the top-level connector object only (e.g. eTDYNDirectory) and allows multiple sensitive values to be obfuscated together.