Option 2.2.2. Start, Stop Project Security

About this task

  • Start, stop security configuration.
  • Start, stop security enabled.

Start, Stop Security Configuration

About this task

Starting and stopping a project can be limited to users who have the authority to make those decisions for the selected project. This includes users who access the project both locally and remotely.

Procedure

  1. In the Project Properties dialog box, in the Options section, select Start stop security.
  2. Close the Project Properties dialog box.
  3. In Workbench, in the left pane, expand the Security folder.
  4. Select Roles.
  5. Double-click a role that will be able to start and/or stop the project.
    The Role properties dialog box opens for the selected role.
  6. Select either the Start Project or Stop Project check box or both.
    A Start Project Users who are assigned this role can start this project.
    B Stop Project Users who are assigned this role can stop this project.
    Note: Make sure that at least one user is assigned a role that has Stop Project privileges.
    Note: When the Start, stop security check box is clear in the Project Properties dialog box, the Start project and Stop Project check boxes are disabled.

Start, Stop Security Enabled

A user may do any of the following to start a project:
  • Use Workbench functionality
    • Toolbar Run button
    • Project>Run menu item
    • Ctrl+R keyboard
  • Access a CimView screen.
  • Log in to a project through the Alarm Viewer
  • Start a project on the Projects tab in the CIMPLICITY® Options dialog box.
  • Open any or the following
    • Point Control Panel
    • Process Control
    • DGR
    • Recipes

When Start, stop security is enabled a Start project dialog box opens.

Fill in both fields.

User ID User ID for a user who is authorized to start the project.
Password User's password.

Allow or Disallow Projects from Running on a Server

CIMPLICITY supports project level security. This enables you run certain projects and reject certain projects from running on a server. To enable this, you must add the projects that are allowed to run on the server to AllowProjects.json file located at <Install_Location>\Proficy\Proficy CIMPLICITY\admin_data. The projects that are not included in the list are not allowed to run. Only an administrator has the permission to edit AllowProjects.json. Sample contents of AllowProjects.json:
 {
  "allow_all": false,
  "allow_projects": [ "C:\\Projects\\Thermal_Project",
                      "C:\\Projects\\Hydro_Project" ]
}
If “allow_all” is set to true, all the projects on the server are allowed to run. This is the default option.

If you want to allow only certain projects to run, you must set “allow_all” to false, and specify the allowed projects in the “allow_projects” list. All the other projects on the server will not be allowed to start.

If you attempt to start a project that is not in the allowed list of projects, an error message is displayed, and the error is logged in cor.log.

The CIMPLICITY Startup Options feature respects AllowProjects.json. That is, if you have added some projects to start on system boot and “allow_all” is set to false, only the projects that are added to “allow_projects” are allowed to start on system boot.