Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2

...

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

  • Added support for ransomware protection using object locking. This includes both configuring bucket-level locking defaults as well as fine-grained object version locking support. (UIC-519, UIC-520, UIC-521, UIC-554)

Upgrade Impacts

Version Requirements:

...

Changes in Content UI 7.3

This release contains support for the System domain, allowing you to use Swarm's modern features such as metadata searching and policy/access control for unnamed and untenanted objects through the UI. See System Domain for Legacy Objects. (UIC-479, 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 are unchanged.

Changes in Content UI 7.2

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

Watch Items and Issues — Same as 7.0.

Changes in Content UI 7.1

...

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

  • Empty folders — The Content UI allows creation and persistence of new, empty folders ready to receive files. This allows you to plan and set up organizing structures ahead of time, to guide content uploaders to use your organization. By having users upload directly to your folders, you can enforce a content architecture and avoid the risk they perform bulk uploads using a malformed prefix.

  • 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). The created folder can be deleted from the flattened view of the folder listing, without disturbing contents or the prefix naming. (UIC-161)

Single Sign-on — The Content UI can now offer SSO (single sign-on) for your 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 your identity providers, such as OneLogin, Okta, or Google. You can implement a single sign-on at the root level and/or for specific domains. See Enabling SSO with SAML. (UIC-212)

...