Skip to main content

Content Manager - Getting started

Content Manager provides functionality for manipulation with files (blobs) and folders structure.

Key features:​

  • Folders - represents virtual folder(info) to organize files into hierarchical groups
  • Files - represent a virtual file(info) decorating blob metadata and blob content
  • Sharing - Creating temporary acccess token to sharing some content from tenant scope level to "anonymous" access.
  • Permission - Role based permission to control content access.

Private / Public storage access​

Common API parameter ContentAccess controls the Tenant / public db context switching:

  • Auto - implicit value, service itself decides which db context(s) will be used (i.e. tenant, public or both), current strategy is using Private db context as default, use this option only when you don't care about db contexts and data privacy.
  • Private - Tenant db context is used, tenant identifier is provided by auth token, use this option when you want to keep privacy of data on tenant level.
  • Public - Public db context is used, tenant identifier is optional, anonymous access can be allowed, use this option when you want to keep data in public storage and share across platform community, your access and manipulation with data can be limited.

Connector for backend usage​

Example: Connector registration​

// Dependency injection configuration
using ASOL.ContentManager.Connector.Extensions;
using ASOL.ContentManager.Connector.Options;

services.AddApiConnectorInfrastructure();

services.Configure<ContentManagerClientOptions>(Configuration.GetSection(nameof(ContentManagerClientOptions)));
services.AddContentManagerClient();
// appsettings.json
{
  // ...
 
  "ContentManagerClientOptions": {
    "BaseUrl": "https://[hostname]/api/asol/cnt"
  },

  // ...
}