Custom Attribute Support

Several enhancements have been made for custom attribute support. They include:

The connector supports up to 50 custom attributes eTLNDCustomAttribute01-50 and up to 50 custom capability attributes eTLNDCustomCapabilityAttribute01-50 (policySync="yes").
Connector Xpress must be used to map custom attributes and custom capability attributes. Mapping custom attributes using XML file <jcs-home>/conf/override/lnd/lnd_custom_metatdata.xml is no longer available.
Only power users should modify the custom metadata file and should take precautions like saving a backup copy of any existing file before updating. Tests to verify mapping changes should be conducted immediately after modifications are made, as any syntax errors introduced will render any LND connector hosted by the modified CA IAM CS inoperable until a valid custom file is reinstated (or the offending custom mapping file deleted).
If customized mappings need to be active on multiple CA IAM CS installations, the same metadata needs to be deployed on each of them.
Attribute values entered on the Custom Attributes tab are subject to validation by the connector. For example, integer fields emit a validation failure when non-digit characters are present.
The values provided for any custom attribute configured to be date or dateTimes on the Custom Attributes tab, must be entered in the UTC time zone, not local time, unless the computers on which the client is running and the LND endpoint are configured to use the same time zone.