Team Trusts tab

At Topology > Teams, you can configure Teams. Use the Trusts tab to define trusted Modules and Resources for the Team.

Availability of the Trusts tab depends on the global setting Trusts Security. See Trusts.

Configuration

  • Use the tabs Trusted Modules and Trusted Resources to define trusted Modules and Resources for the Team.
  • A Team can have explicit Trusts or inherit its Trusts from its Team folder.
  • Use the search bar to search for specific objects.
  • You can use the following settings when configuring Trusts:
    • Do not trust: If this setting is selected, the selected item is not trusted. For example, if you are configuring Trusts on a specific Agent and specify that the Module Delete Ivanti Automation Results is not trusted by the Agent, the Module will fail when used in a Job that is executed by the Agent.
    • Trust: If this setting is selected, the selected item is trusted. This is the default setting. Depending on whether a full Trust exists with the item, it is possible to use the item in a Job. For example, if you are configuring Trusts on a specific Module and specify that Agent ONE is trusted by the Module, the Agent is allowed to use the Module in a Job.
    • Inherit trust: If no particular settings are selected (blank check box), the item will inherit the Trusts from the above lying item. Trusts that are inherited from an above lying item are grayed out and show the type and name of this item, except when this is the top level folder: The Trusts of each top level folder use the default setting (Trust). These Trusts are shown in black and it is not possible to change their settings.
  • All items that are shown on the various Trusts tabs are subject to the access permissions of the administrative role(s) of the Console user.
  • Select Show only items that trust this ... to filter on items that already trust the Agent, Team, Team folder, Module, Module folder, Resource or Resource folder that you are editing. When Trusts are enabled, Agents can only execute Jobs with Modules and Resources when a full Trust exists between them (i.e. the Module or Resource is trusted by the Agent AND the Agent is trusted by the Module or Resource). By using a filter, it becomes easier to create full Trusts.
    • Filtering the Trusts tab may take some time, especially in large environments with many Agents, Modules and Resources. When selecting the option, a popup window is therefore shown, showing the progress. If necessary, you can cancel the filtering.
    • If an item does not trust the item that you are editing, it will not be shown. Folders will be shown with an overlay icon.
    • This option requires Microsoft .NET Framework 4.0 (Full version) or higher to be installed on the machine that runs the Console.
  • When you create a duplicate of a Team for which Trusts have been configured, you will be prompted whether the Trusts should be included in the duplicate.

Agents that use a Team as their primary Team not only inherit its Trusts (Security settings), but also its Team settings (Topology settings). It is therefore recommended to consider the consequences before assigning an Agent to a different primary Team, as this may have a severe impact on the performance of the Agent.

Best practice:
Create a Team folder, configure Trusts on this folder and add the two primary Teams to the Team folder. In this way, it is not necessary to change Team settings or Trusts for each primary Team: the Agent will still inherit the correct settings from its primary Team.