All instance parameters refer to a named instance, hence the common parent in the connect.yaml
configuration file is always tia.instances.<name>.sharepoint
, where <name>
stands for the selected name for the instance.
At least one encryption key definition must be configured, see https://kgs-software.atlassian.net/wiki/spaces/SUPPORT/pages/3558277723/DRAFT+-+Sharepoint+specific+configuration#Encryption-key-definition-parameter .
Archive path configuration
The parameter archiveFolder
specifies the base location in tia Content Server. In addition, attributes from SharePoint request may be used to append to this path. This enables separation of archived data by site, library, or path.
The SharePoint request to tia Connect contains these attributes path
, pathPrefix
, siteId
, and libraryId
. By true
|false
switches, each of these attribute can be included into the storage path. The sequence, however, is fixed.
For example:
When all attributes are included:
archiveFolder/siteId/libraryId/pathPrefix/path
When only
libraryId
andpath
are included:archiveFolder/libraryId/path
Parent | Parameter | Description of request attribute | Required | Supported values | Default |
---|---|---|---|---|---|
|
| CMIS folder in which the data is to be archived Example: | no |
|
|
|
| The strange, anywhere configured, SharePoint path | no |
|
|
|
| A prefix for the archive path | no |
|
|
|
| Sharepoint Site ID | no |
|
|
|
| Sharepoint Library ID | no |
|
|
When path
request attribute is not included, the storage path is not mirroring the SharePoint folder structure. This may result in collisions when files in different SharePoint folders have the same name, and tia Content Server is only archiving the first file, while then for other files with same name archiving results in error.
Create ShareLink configuration
A ShareLink is a link that can be sent to a recipient and allows him to access file from archive. By default, when opening the ShareLink, the recipient will have to authenticate against Microsoft Entra. The authentication mechanism is Open Identify Connect (OIDC).
Parent | Parameter | Description | Required | Supported values | Default |
---|---|---|---|---|---|
|
| Whether access documents via SharedLink should be secured via OIDC or publicly accessible | no |
|
|
Reference data in the ShareLink is encrypted. The encryption is configured by encryption key definitions.
At least one encryption key definition must be configured.
When creating a ShareLink, tia Connect is always encrypting using the last encryptionkeydefinition
in this list. All previous encryptionskeydefinition
are required for decryption at time of opening a ShareLink. Therefore:
If the algorithm currently in use is no longer the most secure choice, configure a new
encryptiondefinitions
at the bottom of the list: The new key will then be used for all new links.Keep old
encryptiondefinitions
in the configuration until no ShareLink created using this definition is entitled to access archive files anymore.
Encryption key definition parameter
Parent | Parameter | Description | Required | Supported values | Default |
---|---|---|---|---|---|
|
| Identifier for the definition | yes |
| - |
|
| The encryption algorithm | no |
|
|
|
| The password for encryption and decryption | yes |
| - |
|
| The secret-key algorithm | no |
|
|
|
| The iteration count | no |
|
|
|
| The to-be-derived key length | no |
|
|
Mapping Metadata
With the setting metadata-mappings
an incoming property can be mapped to a different property on the cmis-side. The mapping also applies when fetching the properties, the cmis-side property is mapped to the original value. The definition of the cmis-side must specify the full cmis-id of the target property.
Examples
metadata-mappings: customvalue: 'cmis:description' othervalue: 'sapbo:basedocument:Document'
The first mapping maps the incoming value customvalue
to the cmis property cmis:description
, which is a default property. The second mapping maps the incoming value othervalue
to the cmis property sapbo:basedocument:Document
. The latter will fail, because the cmis property is a non-standard property. To be used, the type mapping parameter must be added.
type-mappings: "[sapbo:basedocument:Document]": 'sapbo:basedocument'
This setting defines, that whenever the property sapbo:basedocument:Document
is filled, the type sapbo:basedocument
must also be added. In combination with the above metadata-mappings, this means whenever the property othervalue
is filled in an incoming metadata request, either on create or on patch, the type will be added.
Metadata mappings
Parent | Parameter | Description | Required | Supported values | Default |
---|---|---|---|---|---|
|
| CMIS custom type for sharepoint metadata | no |
|
|
|
| Prefix for extension of the sharepoint metadata | no |
|
|
|
| List of meta fields from Sharepoint that should be ignored. Specify this parameter to append to the list in default column. The listed values cannot be unset. | no |
|
|
|
| Mapping of custom property name to CMIS property name. | no |
| - |
|
| Mapping of custom property name to CMIS property name. | no |
| - |
Typedata mappings