Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Changes in Content UI 7.5

  • Added support for Hybrid Cloud Copy to S3.

  • 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.

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

  • Added finer-grained control for data protection policies

  • Third-party software package updates

Upgrade Impacts

Version requirements:

  • Gateway 7.4

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

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, UIC-443)

Watch Items and Issues — Same as 7.0.

Changes in Content UI 7.0

Remote Synchronous Write — Specific domains and buckets can be configured to broadcast the new content to all remote sites immediately in the Content UI. This feature, Remote Synchronous Write, delays write completion until replicas exist in every remote cluster. This setting allows you support applications that require guarantees that backups are committed to every site, and to support publishing requirements to be able to read new content from any remote site immediately after ingesting. 
See Setting Remote Synchronous Write (RSW). 

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 users' file systems. The service makes full use of newer Elasticsearch features and is no longer bound by ES listing limits. See Using Virtual Folders. 

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 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)

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)

  • After upgrading the Content UI (Portal) and/or Storage UI, the cache must be cleared to get the new version. 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)

  • When uploading files from iOS devices, all filenames are "image.jpg". These may be uploaded as UUIDs or upload 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 a 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) 

  • To create a collection from metadata that includes non-ASCII characters, you must create it from the domain page. The ability to create a collection from non-ASCII metadata on the object details page is not currently supported. (UIC-31)

  • For any collections that erroneously show the bucket icon, make a small edit and resave them, which causes them to be fully repaired. (UIC-24)

  • No labels

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.