Taskana Configuration

Taskana is configured via a configuration file 'taskana.properties'. This configuration file contains all parameters to control the behaviour of the taskana library.

General Parameter

Security Configuration

The properties file contains the specification of the lists of access ids (i.e. users or groups) that belong to the roles user, business_admin or admin.

The keywords to specify these roles are as follows:

Each entry may contain a list of access ids that are separated by the '|' character. Whitespace at the begin or end of each access id is ignored. This is, as sample config may look like

taskana.roles.user = group1 | group2

taskana.roles.admin= Holger  |  admingroup1| admingroup2|admingroup3 | uid=john.doe,ou=People,dc=example,dc=com

taskana.roles.businessadmin=busadmgrpa|busadmgrpb | busadmgrpc

By default, this configuration file has the name 'taskanaroles.properties' and is searched in the classpath. In addition, the separator '|' is used. Both defaults can be changed by specifying the property filename and separator explicitely when creating the TaskanaEngineConfiguration via constructor.

 TaskanaEngineConfiguration(DataSource dataSource, boolean useManagedTransactions,
        boolean securityEnabled, String propertiesFileName, String propertiesSeparator)

If in this call, either propertiesFileName or propertiesSeparator is null, Taskana uses the default value.

If for example, you want Taskana to use the 'application.properties' file from the classpath, you should specify "/application.properties" as propertiesFileName.

You may also specify a fully qualified filename that addresses a file directly. In this case, that file is not searched on the classpath but loaded by its name.

Please note, that if you specify a non-default propertiesSeparator, the access ids must not contain any character that is contained in this propertiesSeparator.

If Taskana doesn't find a configuration file, it operates with empty roles.

Job Configuration