Release Notes 3.2.14

Publication Date: November 11th 2018

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.14 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the [Cloud CMS 3.2 Migration Documentation](https://www.cloudcms.com/documentation/docker/maintenance/upgrades.html).

Cloud CMS API

• Support for Multifactor Authentication (MFA - external SMS, Voice or App verification code for sign in) configurable globally as well as per-tenant via service configurations. Initial out-of-the-box providers for Authy and Duo Security. For more information, see [https://www.cloudcms.com/documentation/mfa.html](https://www.cloudcms.com/documentation/mfa.html).
• Added formal support for encrypted properties within API configuration properties files using pub/private keys. This allows passwords, secrets and other credentials to be safe guarded so that they are only read by the API server. For more information, see [https://www.cloudcms.com/documentation/docker/configuration/encrypting-properties.html](https://www.cloudcms.com/documentation/docker/configuration/encrypting-properties.html).
• Ensure node service invalidates for branch when branches are archived
• Added a check to make sure that archived branches are not included in dashlet controllers recent content queries
• Added command line tool to help customers generate pub/private keys and manually encrypt and validate encrypted values within properties files
• Updated third party dependency versions

Cloud CMS User Interface Server

• Added support for Multifactor Authentication (MFA) - services and user settings screens and a new wizard that helps users set up MFA and register their mobile devices. For more information, see [https://www.cloudcms.com/documentation/mfa.html]
• Fixed a bug whereby admin console wouldn't render in some browsers due to a CSS glitch
• Fixed a bug that prevented the Authentication Grant Edit page from working for some grant values
• A message is now shown when an attempt to undeploy a workflow fails
• Fixed a bug that prevented form "view" attributes from being copied back to the Alpaca config ahead of render of a content form (this prevent some layouts and wizards from working as intended in those cases)
• Fixed a bug that prevented the UI from rendering properly after a selected release is archived and the active branch is still being referenced in the browser URL (in this case, the browser URL is deliberately reset to prevent this from happening)
• Document View Properties now shows the edited date instead of the modification date to make it more intuitive and consistent for editorial users
• Fixed a bug that prevent content types (on the left hand side of the Content page) from being sorted correctly
• The "My Projects" dashlet now supports specification of sort (recently created or recently modified with the former being the default)
• Fixed a bug that prevented the Kaltura module's menu options from appearing in the right place