22 August 2018
| Query banding
When multiple Campaign users connect to the same FDA Teradata external account, you can now pass a query band (key/value pairs) specific to each user. Each time a Campaign user performs a query on the Teradata database, Adobe Campaign is now able to send meta data associated to the user. These data, which consist in a list of keys and values can then be used by Teradata administrators for audit purposes or to manage access rights, for example.
For more information, refer to the detailed documentation.
A specific key (PROXYUSER or PROXYROLE) is used to associate a Teradata user or role to a Campaign user. A new permission has been added to use this proxy user/role. You need to add the GRANT CONNECT THROUGH access right to the database account (the one defined in the Teradata external account).
A new tab has been added in the Teradata external accounts. The Query banding tab includes the following options:
For more information on query banding, refer to these articles:
25 June 2018
| Security improvements
|| A series of security improvements has been added to Campaign Classic. Improvements and fixes are listed below.
| Support of Windows Server 2016
|| Adobe Campaign is now compatible with Windows Server 2016. Refer to Campaign Classic Compatibility matrix.
The decryptString function is deprecated. Refer to the Deprecated and Removed Features article.
For new customers, this function is now only used to decrypt the recipient’s crypted ID in landing pages. To decrypt passwords stored in an external account, use the new decryptPassword function.
For existing customers, the behavior of this function is not changed but we recommend that you use decryptPassword instead of decryptString. The XtkSecurity_Unsafe_DecryptString compatibility option is added by the postupgrade and activated by default, allowing you to keep using the function. If you want to deactivate decryptString, deactivate the option.
The decryptPassword function has been added. It allows you to decrypt a password stored in an external account. Refer to the JSAPI documentation for more information.
For new installations, folder access via file APIs is limited to the var, sftp and temporary folders of Adobe Campaign.
For existing customers, file APIs can no longer access the conf folder of Adobe Campaign. The XtkSecurity_Disable_JSFileSandboxing compatibility option is added by the postupgrade and activated by default, allowing you to keep accessing the other folders. If you want to limit the access to the var, sftp and temporary folders of Adobe Campaign, deactivate the option.