Limit/Restrict Command of a Specific Protocol

Introduction:

The file ops protocols as SSH/SMB2 (that can be used for any commands ) can give us more information than expected, like IP/Hostname resolution. To limit those protocols to do exactly the process we need (like installing the connector only), JetPatch made specific configuration parameters helping limit those protocols to a particular command.

To do so we will need to add some configuration in the "intigua.config.xml" located in 

"usr/share/tomcat/default/conf/intigua.config.xml" and then restart tomcat.

Important:

1. The parameters need to be added between  "<system>" and "</system>" tags. 
2. The Indentation need to be respected 
3. Each command "<support-commands>INSTALL_VLINK</support-commands>" need to be on single line.

In the example below we are limiting SSH and SMB2 to install connector only (inserted right before the end of </system>)

<system> 
... 
  <ssh> 
    <support-commands>INSTALL_VLINK</support-commands> 
  </ssh> 
  <smb2> 
    <support-commands>INSTALL_VLINK</support-commands> 
  </smb2> 
</system>

List of protocols available:

VSPHERE
CIFS
WEB
SSH
WINRM_SMB
SMB2
AZUREVMEXT

START
STOP
RESTART_SERVICE
GET_STATUS
INSTALL_VLINK
UNINSTALL_VLINK
UPGRADE_VLINK
UPGRADE_VLINK_LOADER
UN_VIRTUALIZE
UN_VIRTUALIZE_KEEP_PACKAGE
UPDATE_CONFIG
RECONFIGURE_VLINK
FILES_LIST
FILE_CONTENT
GET_FILE
DELETE_FILE
CONNECTOR_DATA_PACKAGE
GET_VAGENT_CONFIG
GET_VAGENT_PACKAGE
UPDATE_VAGENT_CONFIG_ID
COLLECT_ENDPOINT_DATA
UPDATE_DETECTION_DIRECTORY
RUN_SCRIPT
RUN_SCRIPT_TO_FILE
INVOKE_RUNNABLE
UPDATE_DISCOVERY
PATCHING_READINESS
NOTIFY_REBOOT
TAKEOVER_VAGENT