Versions Compared

Old Version 49

changes.mady.by.user Simone Conrad

Saved on

compared with

New Version Current

changes.mady.by.user Matthias Rieck

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Parameter Name

DataType

Optional

Default

Description

Example/Values

Available since Version

type

String

no

Definition of Content Service type.

azureblobstorev2

connectionstring

String

noyes

Azure Connection String. Is obsolete if storageendpoint is set.

DefaultEndpointsProtocol=https;AccountName=<azurename>;AccountKey=<tiacore/UA==>;EndpointSuffix=core.windows.net

2.0.8

storageendpoint

String

yes

Used for Azure Managed Identity.

Azure storage endpoint. If this is set the connectionstring is obsolete. Is uses with priority over connection string.

https://mystorageaccount.blob.core.windows.net/

3.8.0

container

String

no

Azure Container Name.Azure | [inlineExtension]Naming Conventions:

mycontainer

2.0.8

contrepinpath

Boolean

yes

true

Root folder starts with Repository Syntax.

true/false

2.0.8

cleanversions

Boolean

yes

true

true = deletes all previous versions for "UPDATE" and "DELETE" operations in buckets with versioning.

false = all versions still persist.

true/false

1.9.0

calculatestreamhash

Boolean

yes

true

After successful encryption, the hash values are recalculated.

true/false

2.0.8

invalidcharacters

String

yes

This parameter can be used to define additional characters that require the name to be encoded for Azure.

<user>, z.B. \uFFFE\uFFF9\uFFF0

2.0.8

region

String

yes

azure

Selection of the region for the creation of a new container.

azure, germany, us, china

2.0.8

minparallelsize

Num

yes

4194304

Limit for upload in bytes for parallel upload with multiple threads.

2.0.8

maxconcurrency

Num

yes

2

Maximum amount of threads for parallel uploads.

2.0.8

blocksize

Num

yes

4194304

Blocksize in Bytes for parallel upload.

2.0.8

singleuploadsize

Num

yes

4194304

Chunk size for parallel upload in bytes.

2.0.8

...

Code Block
<Repo>.contentservice.azureblobstorev2.type = 
<Repo>.contentservice.azureblobstorev2.storageendpoint =
<Repo>.contentservice.azureblobstorev2.connectionstring = 
<Repo>.contentservice.azureblobstorev2.container = 
<Repo>.contentservice.azureblobstorev2.contrepinpath = true 
<Repo>.contentservice.azureblobstorev2.cleanversions =  true
<Repo>.contentservice.azureblobstorev2.calculatestreamhash = true
<Repo>.contentservice.azureblobstorev2.invalidcharacters= 
<Repo>.contentservice.azureblobstorev2.region = azure
<Repo>.contentservice.azureblobstorev2.minparallelsize = 4194304
<Repo>.contentservice.azureblobstorev2.maxconcurrency = 2
<Repo>.contentservice.azureblobstorev2.blocksize = 4194304
<Repo>.contentservice.azureblobstorev2.singleuploadsize = 4194304

...

To use this feature, it is necessary to create a container with the "version-level immutability" option. See: https://learn.microsoft.com/en-us/azure/storage/blobs/immutable-policy-configure-version-scope?tabs=azure-portal

tia Content Server will manage the retention periods do not set default retention times on Azure.

This can be enabled in the Azure StorageAccount in a manually creation process of a container or via a corresponding configuration in tia Core, which is described below.

...

Code Block
<Repo>.contentservice.azureblobstore.container=test1                    # Container for metadata and retention information
<Repo>.contentservice.azureblobstore.container.retention.0=test-0       # Container for expired documents

Managed Identity

Managed Identity bewares you of copying and configuring security relevant parameters. It only works if blob store and tia core is hosted in Azure. (Same is valid for SQL db)

Azure knows 2 kinds of managed identity. Tia core can use both. Here shown is only server managed identity. On tia core configuration this distinction has no influence.

Managed Identity (Storage Account)

The blob store needs to have the role “Storage Blob Data Contributor”. There you add the app id of tia core. Then you can configure for blob store the storageendpoint instead of connectionstring.

Here the way to allow tia core to use managed identity.

  • enter resource group

    image-20240904-144811.pngImage Added

  • select your resource group or create a new one

  • select your storage account:

    image-20240904-144923.pngImage Added

  • enter access control (IAM):

    image-20240904-145022.pngImage Added

  • Add a roll “Storage Blob Data Contributor”

    image-20240904-145146.pngImage Added

  • use search bar and enter enter: storage Blob Data Contributor

    image-20240904-145343.pngImage Added

    • press next

  • press select members

    image-20240904-145508.pngImage Added

  • paste the tia core app id in search bar

    image-20240904-145559.pngImage Added

    • press select

    • press review and assign