Changing Agent Controller security settings after installation


To change the desired level of security:

  1. On machines where Agent Controller is installed, run the SetConfig script (SetConfig.bat for Microsoft Windows platforms; SetConfig.sh for non-Windows platforms), which is located in the bin subdirectory of the Agent Controller installation directory.
  2. Press the Enter key to keep the JRE path setting.
  3. For the Network access mode setting, specify ALL, LOCAL, or CUSTOM to specify which network hosts can access this Agent Controller.
  4. If you specify ALL, it is recommended that you turn security on (see following steps) to ensure there can be no unauthorized access to the machine. Unless you turn on security, the ALL setting provides a security level of None, as described in the Security overview .
  5. If you specify LOCAL, only the local Workbench can access Agent Controller, providing the Local access only level of security described in the Security overview .
  6. The CUSTOM setting provides the Specific hosts only setting described above, and the additional security options below may be used or not used at your own discretion. CUSTOM without security is the recommended setting for those using LDAP security, for example.
  7. If you specified CUSTOM, the script prompts you for a list of fully-qualified host names or IP addresses, separated by comma, which are allowed to access Agent Controller on this machine.
  8. For the Security enabled setting, to turn security on, type TRUE. To turn it off, type FALSE. It is especially recommended that you specify TRUE if you have specified ALL for the Network access mode setting.
  9. If you turn security on by typing TRUE, the script will prompt you to specify which users can access Agent Controller. Specify that any user can access by typing ANY, or specify a list of specific user names (IDs), separated by commas, that can access Agent Controller on this machine. When users attempt to access Agent Controller (whether ANY or a list were specified), they will be required to authenticate by entering their system password. This provides the Full security enablement level described in the Security overview.
  10. Press Enter at the remaining prompts to finish running through the SetConfig script without changing other settings.
Note iconNote

Host access control is not implemented for the TPTP_SOCKET transport layer, therefore it does not restrict host access in any way. If you wish to control host access and you are not using any components that require the new technology protocol (currently only the JVMTI agent requires this), you should remove the TPTP_SOCKET TransportLayer section from your serviceconfig.xml file.

Related concepts
Security overview



Copyright (C) 2006 Intel Corporation.