Changes in Content UI 7.8

• Improved support for loading Content Portal with a user session created from outside Content Portal (UIC-645)

• Refreshed look and feel

Upgrade Impacts

• Version Requirements

  • Gateway 7.10.3

Watch Items and Issues

Same as 7.7

Changes in Content UI 7.7

• Added support for new Hybrid Cloud features, including repatriation of remote content from the cloud to swarm as well as support for Azure endpoints. (UIC-600)

• Fixed an object locking issue related to Veeam integration. (UIC-607)

Upgrade Impacts

• Version Requirements

  • Gateway 7.10.0

Watch Items and Issues

Same as 7.6

Changes in Content UI 7.6

Added support for https://perifery.atlassian.net/wiki/spaces/public/pages/2927099905/Bucket+Lifecycle+Policy?search_id=5df4fec5-f1d5-4d8b-a9b1-723d836c7b0b with S3 and SCSP. (UIC-570)

Upgrade Impacts

• Version Requirements

  • Gateway 7.9

Watch Items and Issues

• When attempting to delete all versions of an object with locking applied to at least one version, the operation fails. (UIC-577)

• When an object is locked, the delete operation may still be available on that object. This behavior mirrors S3. The protected version(s) are still present, protected, and accessible in the storage cluster, but the object is longer be visible in Content UI. This happens due to the delete marker available in the "current version". To make the object visible again, either use an S3 tool to remove the delete marker or upload a new version of the object. (UIC-576)

• Inherit Versioning in domain or bucket properties is not working as expected. To make the versioning work, both domain and bucket settings must be "Enabled" and Swarm settings policy.versioning must be "allowed". (UIC-272)

Changes in Content UI 7.5

• Added support for Hybrid Cloud Copy to S3. (UIC-539, UIC-540, and UIC-550)

• Added support for ransomware protection using https://perifery.atlassian.net/wiki/spaces/public/pages/2898919491/Object+Locking?search_id=1b5b5969-1a9f-4232-a295-652df22e8543. This includes both configuring bucket-level locking defaults as well as fine-grained object version locking support. (UIC-519, UIC-520, UIC-521, and UIC-554)

Upgrade Impacts

• Version Requirements

  • Gateway 7.8

Watch Items and Issues

• When attempting to delete all versions of an object with locking applied to at least one version, the operation fails. (UIC-577)

• When an object is locked, the delete operation may still be available on that object. This behavior mirrors S3. The protected version(s) are still present, protected, and accessible in the storage cluster, but the object is longer be visible in Content UI. This happens due to the delete marker available in the "current version". To make the object visible again, either use an S3 tool to remove the delete marker or upload a new version of the object. (UIC-576)

• Inherit Versioning in domain or bucket properties is not working as expected. To make the versioning work, both domain and bucket settings must be "Enabled" and Swarm settings policy.versioning must be "allowed". (UIC-272)

• For tenant users to be able to navigate to the own domain, grant them ListDomains permission in the tenant policy. Content Portal is missing that action, but it can be added in the policy via JSON text editor. See Content UI Installation. (UIC-580)

Changes in Content UI 7.4

• Added drag-and-drop functionality within the folder listing views. (UIC-451)

• Added finer-grained control for data protection policies. (UIC-457, UIC-458, and UIC-459)

• Third party software package updates. (UIC-464)

• Added support for browsing untenanted objects via the “SYSTEM DOMAIN”. (UIC-445)

Upgrade Impacts

• Version Requirements

  • Gateway 7.4

Changes in Content UI 7.3

This release contains support for System domain, allowing use of Swarm's modern features such as metadata searching and policy/access control for unnamed and untenanted objects through the UI. See System Domain and Legacy Mode for Gateway. (UIC-479 and UIC-445)

Watch Items and Issues

• Removes operational limitation of using single sign-on with tenant-level IDSYS or logins with user+tenant style user names. (CLOUD-3229)

• Remaining items from 7.0 unchanged.

Changes in Content UI 7.2

This release contains improvements to SAML behaviors and token handling for tenants. (UIC-454, UIC-453, and UIC-439)

Watch Items and Issues

Same as 7.0.

Changes in Content UI 7.1

Updating to this version is recommended to resolve potential issues with the setup of Remote Synchronous Write and with moving between the Content and Storage UIs. (UIC-441 and UIC-443)

Watch Items and Issues

Same as 7.0.

Changes in Content UI 7.0

Remote Synchronous Write: In the Content UI, configure specific domains and buckets to broadcast new content to all remote sites immediately. This feature, Remote Synchronous Write, delays write completion until replicas exist in every remote cluster. This setting allows support applications requiring guarantees backups are committed to every site, and to support publishing requirements to be able to read new content from any remote site immediately after ingest. 
See https://perifery.atlassian.net/wiki/spaces/public/pages/2443818831?search_id=5346c043-c0f3-4a31-a66f-8395c3fad169. 

Folder Listing UI: With Gateway 7, folder listing support across Swarm clients (Content UI, SwarmFS, and S3) has been rearchitected and centralized. Folder listing is what renders the virtual folders (prefixes) on named Swarm objects (such as FY2019/Q3/object.jpg) in to familiar folders on the users' file systems. The service makes full use of newer Elasticsearch features and is no longer bound by ES listing limits. See https://perifery.atlassian.net/wiki/spaces/public/pages/2443819688/Using+Virtual+Folders?search_id=ae9870bc-be4a-491d-9c46-0b6fb60879d7. 

The Content UI now presents these folders as walkable directories, with these key benefits:

• Prefix Filtering: The Content UI provides users a fast and intuitive way to automatically view and manage content in a bucket by parsing object prefixes in to hierarchical folders in real time.

• Empty Folders: The Content UI allows creation and persistence of new, empty folders ready to receive files. This allows planning and setting up organizing structures ahead of time, to guide content uploaders to use the organization. A content architecture can be enforced and avoid the risk users perform bulk uploads using a malformed prefix by having them upload directly to folders.

• Recursive Deletes: The folder listing feature of Content UI includes the convenience of recursive delete (deleting the folder, contents, as well as any subfolders and contents). From the flattened view of the folder listing, the created folder can be deleted without disturbing the contents or the prefix naming. (UIC-161)

• Single Sign-On: The Content UI can now offer SSO (single sign-on) for users through the new SAML 2.0 support in Content Gateway. The login page detects any SAML configuration for the requested host or domain and redirects the user to log in with the identity provider, such as OneLogin, Okta, or Google. Single sign-on can be implemented at the root level and/or for specific domains. See https://perifery.atlassian.net/wiki/spaces/public/pages/2443816877/Enabling+SSO+with+SAML?search_id=8134aa55-eba8-47b0-a0d7-ec5dfdd79755. (UIC-212)

Watch Items and Issues

These are current operational limitations:

• Single sign-on does not support tenant-level IDSYS or logins with user+tenant style user names. (CLOUD-3229)

• The cache must be cleared to get the new version after upgrading the Content UI (Portal) and/or Storage UI. Either shift-Reload the page or clear the browser cache, then verify the About page shows the new version. (UIC-222)

These are known issues:

• Under the Permissions tab, the Access Policy wizard offers Actions related to Tokens, but these are incompletely implemented. Denying users the ability to create tokens prevents them from accessing the Content UI. (UIC-406)

• All filenames are "image.jpg" when uploading files from iOS devices. These may be uploaded as UUIDs or uploaded one file at a time with a different filename prefix. (UIC-188) 

• The login button for the Content UI may require a second click to proceed. (UIC-98) 

• New tokens with user-supplied description do not initially show the description in the list of tokens. Workaround: Refresh the list of tokens after adding a new token. (UIC-43) 

• Create a collection from the domain page to create it from metadata including non-ASCII characters. The ability to create a collection from non-ASCII metadata on the object details page is not currently supported. (UIC-31)

• Make a small edit and resave a collection for any erroneously showing the bucket icon, which causes them to be fully repaired. (UIC-24)