<usertool> - User tool and proxy Definition
The user tool tag defines all the tools that are available to be used to access a device.
These are chosen in a profile and appear under each device that use the template and have been connected together through a profile.
<access> tags define exactly how this access happens.
This tag has the following attributes:
- display_name (str): This is the display string used in the PAM UI* on the link for the tool under the device.
- protocol (str): The name of the protocol the tools uses. This also tells Osirium PAM what type of proxy to use to facilitate the connection.
- launch_script (str): The name of the .au3 file the tool is launched with.
- map_launch_type (local, profile):This defines which type of account is used to establish the underlying RDP RemoteApp connection to the MAP server.
MAP Launch Type Values
map_launch_type attribute can have the following values:
|local||This tells Osirium PAM to create a MAP_USER_
|profile||This tells Osirium PAM to use the same account in the underlying RDP RemoteApp connection as defined in the profile for accessing the target device. This can be a domain account. To use a domain account the MAP server must be a domain member.|
This example shows a device that has three user tools available: SSH, a web browser interface and a thick management client:
1 2 3 4 5
This example shows a MAP tool that will be launched with a local MAP Server RDP RemoteApp account:
1 2 3
This example shows a MAP tool that will be launched on the MAP Server over RDP RemoteApp with whatever account has been defined in the profile:
1 2 3
Any protocol referenced in a
<usertool> tag MUST have a corresponding
<access> tag referencing that protocol. Any
<usertool> element that uses a launch_script, does not need a corresponding access definition.