Subconfigurations

Subconfigurations can be used to override server settings for connections from a specific location or by a user or group. Supported server settings specified in a subconfiguration will replace the default settings given in the VShell Control Panel.

When a connection is made, VShell reviews its location Source subconfiguration list to see if the connected location appears on the list. If the location matches a Source entry, that subconfiguration is applied and takes precedence over the VShell default configuration.

Note: When a location subconfiguration is applied, only settings specified in the subconfiguration are overridden. Settings that are not specifically changed retain their default value.

When a user authenticates, VShell reviews its User/Group subconfiguration list to see if that user appears on the list. If the user or group matches a User/Group entry, that subconfiguration is applied and takes precedence over any location subconfiguration as well as over the VShell default configuration.

Note: When a user or group subconfiguration is applied, only settings specified in the subconfiguration are overridden. Settings that are not specifically changed retain their current value.

Subconfiguration settings must be specified in a .xml file. The following is an example subconfiguration file that contains all the settings that can be overridden using subconfigurations.

<?xml version="1.0" encoding="utf-8" ?>

<Item Type="string">password</Item>

<Item Type="string">publickey</Item>

</AuthenticationsAllowed>

<Item Type="string">password</Item>

</AuthenticationsRequired>

<Item Type="string">I,deny,127.0.0.1,0,Deny localhost</Item>

<Item Type="string">N,allow,0.0.0.0/0.0.0.0,0,Default Allow All Entry</Item>

</PortForwardFilterTableV2>

<UserShell Type="string">C:\WINDOWS\system32\CMD.EXE</UserShell>

</VShell>

Note: The AuthenticationAllowed setting can only be overridden on a location basis.