Editing RD Launchers
On the related Secret Template page, under the Mapping tab, in the Launchers section, click Edit next to the Remote Desktop launcher to modify the settings for a launcher that has already been added to the template.
Click Edit next to the Launcher mapping section to define which fields from the Secret will be passed to the launcher: Computer, Domain, Password, Username. For a launcher to work properly, Secret Server requires credentials to be taken from secret text-entry fields. Fields must be assigned their corresponding credentials from the list. In addition to the secret fields, the domain can be mapped to <blank>
, which passes an empty string to be used with local accounts, and the machine or host can be mapped to <user input>
, which prompts the user for a specific machine to be used with domain accounts.
Click Edit next to the Launcher restrictions section to restrict values that can be passed to a launcher.
-
Restrict User Input: Check to enable restriction. In cases where there are multiple endpoints to connect to, such as with a domain account, the machines can be restricted to a set list. You may specify a field of comma separated hosts or IP addresses that the user will be restricted to. The allow list will allow only these values, while the block list will allow all values except the hosts on the Secret Field. Example: 192.168.1.2, MACHINE.EXAMPLE.COM, 192.168.1.60
-
Use list fields: Indicates where or not globally defined lists will limit the user input. Requires that this template has a field of type List or URL List.
-
Allow list: User can select from values in this list.
-
Deny list: User cannot enter these values. If used with an Allow List, the Deny List will take precedence.
-
Include machines from dependencies: Check to add the list of machine names from the secret dependencies to either the allow list or block list.