Alfresco Configuration

The full and incremental content synchronization as well as the security synchronization do not require any specific preparation of the Alfresco instance.

However the connector uses a technical user to synchronize content and security information and this user must have read privileges for all relevant content.

  1. In order to access a site, the technical user or one of his groups must be included in the site permissions (there is no constraint as to which of his groups should be included). This should hold for all the sites to be indexed.

  2. All folders and documents in a site must inherit parent permissions. If a folder or a doc- ument does not inherit parent permissions, its permissions must explicitly include the technical user or one of his groups.

Content for which the technical user has no read privilege will not be indexed. There will be no warning about such absent content.

Change processing

Alfresco offers a content auditing feature which can be utilized by the Alfresco Connector for change processing. The essential aspect of content auditing is the so-called changelog token, which refers to a specific change. In this section, we will discuss how to enable content auditing in Alfresco.

Enable change processing

Content auditing can be enabled by adding the following properties in the file <alfresco-inst-path>/tomcat/shared/classes/alfresco-global.properties:

audit.enabled=true
audit.alfresco-access.enabled=true
audit.cmischangelog.enabled=true
audit.filter.alfresco-access.default.enabled=true
audit.tagging.enabled=true
audit.alfresco-access.sub-events.enabled=true
audit.dod5015.enabled=true
audit.config.strict=false
audit.filter.alfresco-access.transaction.user=~System;~null;.\*
audit.filter.alfresco-access.transaction.type=cm:content;cm:folder;st:site
audit.filter.alfresco-access.transaction.path=/sys:archivedItem;/ver:;.\*
audit.filter.alfresco-access.default.path=/app:company_home/st:sites.\*

As the Alfresco Connector uses CMIS as the interface for content retrieval, the property audit.cmischangelog.enabled=true is crucial to make content auditing visible in CMIS.

Verify change processing is enabled

To verify that content auditing is visible in CMIS, one can issue the following HTTP request:

curl http://<alfresco_url>/alfresco/api/-default-/public/cmis/versions/1.1/browser

and verify the following in the JSON response:

  • The value of capabilityChanges is not none.

  • the value of latestChangeLogToken is not null.