Enable and Disable Security for a Repository

Introduction

This section explains how to enable or disable the security at repository level. Before you enable/disable security, you must know what is security and how the security will effect the application.

How Does Security Affect the Application?

AVEVA Work Tasks has new enterprise rights and security features. The rights and security can be defined for groups and users can be mapped to groups. The user will be entitled to perform only those tasks for which the right has been given to respective user.

AVEVA Work Tasks has some pre-defined security groups and each security group has default security rights.Pre-Defined Security Groups:

In AVEVA Work Tasks, while creating a repository: user will be asked to set the administrator at repository level. Once you select a user, then the selected user has been added with administrative privileges. This user can create new users, new roles, and new security groups, mapping users/roles with different security groups at different levels (either repository or list or list item levels) and setting security rights for different security groups at different levels.

How to Check Whether Security is Enabled or Disabled for a Repository?

Whether security is enabled or disabled for a specific repository, depends on the Properties Column (properties collection) of SKRepository table in the Farm Database.

For example, find below the Properties column (properties collection) data for a repository.

<properties>  

<property key="sourceelements">

<![CDATA[WORKFLOWELEMENTS\Default]]>

</property>

<property key="fromemail"><![CDATA[admin@domain.com]]></property>

<property key="toemail"><![CDATA[admin@domain.com]]></property>

<property key="alertuser"><![CDATA[False]]></property>

<property key="filewatcher"><![CDATA[]]></property>

<property key="enablesecurity"><![CDATA[True]]></property>

<property key="isadminconfigured"><![CDATA[True]]></property>  

<property key="theme"><![CDATA[Default]]></property>

</properties>

The line highlighted in red in the above code, is used to identify whether security is enabled or disabled for a repository. In this line, you can identify the following:

Enabling security for a repository

In AVEVA Work Tasks, once you create a repository, the security will be enabled by default for that repository.

If you want to enable security for a repository, then open the SKRepostiory table in the Farm Database and find out the required repository entry (row) and in that specific row in properties column data (properties collection) find out the enablesecurity key and update the <![CDATA[False]]> to <![CDATA[True]]>.

Note: If the enablesecurity key is not found for a repository entry in the properties column then add the following line between <properties> & </properties> tags.

<property key="enablesecurity"><![CDATA[True]]></property>

Now the security is enabled for that repository. If you want to enable security for another repository do the same as mentioned above.

Disabling security for a repository

In AVEVA Work Tasks, once you create a repository security will be enabled by default for that repository.

If you want to disable security for a repository, for which the security already enabled, then open the SKRepostiory table in the Farm Database and find out the required repository entry (row) and in that specific row in properties column data (properties collection) find out the enablesecurity key and update the  <![CDATA[True]]> to <![CDATA[False]]>.

Note: If the enable security key not found for a repository entry in the properties column then add the following line between <properties> & </properties> tags in case if you want to enable security in future.

<property key="enablesecurity"><![CDATA[False]]></property>

Default Behavior of Repositories Created in AVEVA Work Tasks

In AVEVA Work Tasks, if you create a repository, then security will be enabled by default for that repository. While creating repository user will be asked to set the administrator for that repository, once the user select the user for administrator, the selected user will be added with administrative privileges for that repository.

Once the administrator user is logged in, they can access the security settings (Repository Settings – top right corner). Any user other than the one belonging to the Administrator security group cannot access the security settings page