Service ACL Service
The service ACL service administers service ACLs.
Service ACLs enable repository services to assign service-specific permissions to users, groups, or roles. Service ACLs work just like standard Framework ACLs (read, write, delete, and so on), and are maintained in the same way as standard ACLs, but the supported permissions are specific to particular services.
To enable a repository service to use service ACLs, the service ACL service must be registered with the relevant repository.
You registered the status management service with a repository. To be able to give certain users the permission to change the approver list for a folder in that repository you must also register the service ACL service.
The status management service is actually a special case insofar as it requires the service ACL service as a prerequisite. Other repository services require the service ACL service to be able to assign certain permissions, but can also be used without it.
The security manager configuration acl_jdbc_service is specified in the standard delivery for the service ACL service.
Service ACL Service Parameters
| Parameter | Required | Description |
|---|---|---|
|
Service ACL Manager Factory |
Yes |
Name of the ACL security manager configuration to be used (see ACL Security Managers ). |
The service ACL service is preconfigured and activated in the KM standard configuration. Normally, you do not need to change its configuration.
Do not deactivate the service.
To check the configuration of the service ACL service, choose Content Management → Repository Services → Service ACL Service.