Cloud CMS Release 3.2.17

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.17 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.


  • Tree API now handles multiple leaf paths and logs invalid leaf paths instead of throwing an exception that had previously failed the entire operation
  • Improved branch auto-maintenance methods to handle automatic cleanup of dangling graph associations between content instances
  • Allow the OAuth 2.0 refresh token race condition window to be customized via properties file
  • Updates to MongoDB collection indexes for faster performance
  • Improvements to the internal management of access tokens, refresh tokens and virtual hosting to make things more efficient and automatic for developers, including new properties file settings to finely control access token and refresh token expiry periods at a Docker config level
  • Added a Spring-config driven way of enforcing the deletion of older access tokens on server restart.
  • Adjusted controller method that reports activities to UI so that activities are always scoped to the projects that a user is a member of.
  • Improvements to Job Queue to more effectively use timestamp ordering of queue elements.
  • Transfer Export job is now phased to allow for AWAIT state while child export jobs execute.
  • Improvements to SSO user sync profile so that everything now occurs server side within a cluster-wide lock, removing the need for app server to establish and maintain this lock.
  • SSO user sync now automatically adjusts user name based on SAML Assertion or JWT profile derived user name.
  • ACL checks on Application datastores now check Project stack if Application belongs to a Project
  • Fixed a bug wherein failed deployment packages could leave deployment records in a processing state.
  • Update to latest Gitana Commons library

Cloud CMS Application Server

  • SSO user synchronization now uses a server-side method, reducing the overhead inside of the app server and removing the need for an app-server scoped lock
  • Improved handling of access token renewal and refresh token management within SSO layer
  • Reduced SSO logging (use environment variable CLOUDCMS_AUTH_FILTER_LOGGER_ENABLED = "true" to enable)
  • Proxy passthrough now supports automatic refresh token processing
  • Added some performance optimizations within caching layer (null sentinel values)

Cloud CMS User Interface Server

  • Fixed a bug whereby some UI extension overrides for custom whitelabel logos might not apply for login screens (including SSO and Multifactor Authentication screens). These branding elements are now consistently restored throughout.
  • Fix sop that Related Content field supports empty {} objects by interpreting as null for relator pickers
  • Improvements to Administration Console management pages for Web Hosts, Auto Client Mappings and Applications
  • Project Search Selected... actions are now configurable via config service
  • Fixed a breadcrumb link within the Content Model Builder
  • Project Listing pagination controls now automatically hide for editorial users (non owner/manager)
  • Fixes and Improvements to CSS

Cloud CMS JavaScript / Node.js Driver

  • Consolidated releases so that NPM distribution supports browser environments (including React.js) without any further work making dependency management easier
  • Better handling of HTTP State on Refresh Token timeout
  • Updates to Auto Client Mapping methods
  • Added GraphQL Query execution and Schema retrieval methods

Cloud CMS Command Line Client

  • Added an administrative command to rebuild MongoDB indexes for a given data store (optional recursing into child data stores)

Get Started with Cloud CMS

It's Free to Sign Up. No Credit Card Required.