Regulate Access to Accelerator

To regulate access to Accelerator, the security file vnc.swd/security.tcl must be edited. To deploy the changes after editing the file, Accelerator must be reset.

The format of the security file is:
vtk_security username|-group vovusergroupsecurity-levelhost1 ...

The security levels are USER, LEADER, and ADMIN. Security-level roles can be assigned to users or groups of users (VovUserGroups). VovUserGroups are created from user lists manually, or by associating them with existing UNIX or LDAP groups. For more information about VovUserGroups, refer to VovUserGroups in the VOV Subsystem Administrator Guide.

Both the administrator and root should be granted the ADMIN role; all others should be granted the USER role.
Note: For vovtaskers to work correctly, root must also be granted the ADMIN role.

Disable Security

Security can be disabled by allowing unrestricted access to all users to Accelerator; assign everyone ADMIN privileges from all hosts.
# This is the vnc.swd/security.tcl file needed to disable security.
# The first + means "everybody"
# The second + means "from all hosts"
vtk_security + ADMIN +  

Enable Security

To control access to Accelerator, activate security. The minimum requirement is that both the administrator and the root of Accelerator must have the ADMIN level of privilege from all hosts.

Shown below is an example of a security file. In this example, the system uses five computers. User "john" can only use the system from host ws1, and user "susie" can use the system from hosts ws1 and ws2. Users in the VovUserGroup mygroup have ADMIN rights on the set of hosts known as $allHosts.
# Example of vnc.swd/security.tcl file
set allHosts { ws1 ws2 apple orange pear }
vtk_security vncadmin ADMIN  $allHosts
vtk_security root     ADMIN  $allHosts
vtk_security john     LEADER ws1
vtk_security susie    LEADER ws1 ws2
vtk_security -group mygroup  ADMIN  $allHosts
vtk_security +        USER   +      
After configuring the security file, Accelerator must be reset to apply those the changes:
% ncmgr reset