...
| 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 |
...
| 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
select your resource group or create a new one
select your storage account:
enter access control (IAM):
Add a roll “Storage Blob Data Contributor”
use search bar and enter enter: storage Blob Data Contributor
press next
press select members
paste the tia core app id in search bar
press select
press review and assign