loadplatform

Some target system types listed on the Target system information page are defined by scripted platform definition files that call a binary agent such as the SSH scripted agent (agtssh) and specify a configuration script that defines supported operations.

Scripted platform definition files are written in the following format:

# KVGROUP-V2.0
   <name> = {
     agent = <binaryToRun>;
     script = <script>;
     category = <category>;
     platform = <platformId>;
     description = <languageTagName>;
   }

for example:

# KVGROUP-V2.0
   agtssh-sample = {
     agent = agtssh.exe;
     script = sampleScript.cfg;
     category = SCRIPT;
     platform = AGTSSH-SAMPLE;
     description = !!!AGTSSH-SAMPLE-DESC;
   }

The keys in the scripted platform definition file are all required and are all case-sensitive. The "category" must be a valid platform category. These are described in platcat.csv in the agent\dat directory.

To load a new scripted target system type:

Scripted platform definition files and configuration scripts can also be loaded from other directories outside the agent directory. To do this, place both the configuration script and the .con file into the desired directory and run loadplatform with the absolute or relative path to the .con file. For example:

loadplatform -a <con filename>.con -d "C:\path\to\agent"

SQL scripted connectors also support defining managed identities by using a configuration file in following format:

 # KVGROUP-V2.0
   <name> = {
     agent = <binaryToRun>;
     script = <script>;
     category = <category>;
     platform = <platformId>;
     description = <languageTagName>;
     objects = <object type>;
   }

for example:

  # KVGROUP-V2.0
   agtoracustom = {
     agent = agtorascript.exe;
     script = agtoracustom.cfg;
     category = ATTAP;
     platform = ORACUSTOM;
     description = "Custom oracle target";
     system = false;
     objects = {ACCT;ASSET;GRP;ROLE;};
  }

Providing managed identities in the configuration file allows connectors to be loaded with only operations related to the specified objects.

Bravura Security Fabric can load a new platform category dynamically. Connector Pack 1.1 or later is required.

To load a new platform category:

This loads the new platform category into the platcat table.

Bravura Security Fabric can load default attributes for connectors from attribute files located in agent\dat directory. The default attributes for connectors are defined in different files which may include account attributes file, group attributes file and object attributes file depending on the connector supported operations.

To load the default attributes:

This loads or modifies the default attributes for the connector platforms by populating attrdef and attrdefval tables.

You should be able to find default attributes for account and group under Manage the system > Resources > Account attributes or Manage the system > Resources > Group attributes then select the connector target system type or the connector target system.

Bravura Security Fabric can load target system discovery templates dynamically. Connector Pack 3.1.0 or later is required. By default, they are located in the agent\dat directory.

Discovery template files are written in the following format:

KVGROUP-V2.0
templates = {
  <TARGET_TEMPLATE> = {
        name = <PSLang name description>
  
        address = <PSLang address description>
        <key> = <value>; # target system option
        ...
        ...
        <key> = <value>;
           Resources = {
           };
           TargetAttrs = {
           };
  };
}

for example:

# KVGROUP-V2.0
templates = {
  NT_TEMPLATE = {
    name = "$comp[\"dNSHostName\"][0]";
    address = "\"{server=\" + $comp[\"dNSHostName\"][0] + \";}\"";
    runlist = true;
    listattributes = true;
    listgroups = true;
    idarchivepush = true;
    adminresethide = true;
    selfresethide = true;
    adminunlockhide = true;
    selfunlockhide = true;
    adminclaimhide = true;
    selfclaimhide = true;
    selfmanagehide = true;
    listmembertype = A;
      Resources = {
        ls_scmacct;
        ls_taskacct;
        ls_iisacct;
        ls_comacct;
        ls_normacct;
       };
     TargetAttrs = {
       ADDR_ATTR = "DNSHOSTNAME";
       DESC_ATTR = "DNSHOSTNAME";
     };
  };

The keys in the discovery template file are all required, and are all case sensitive. The name and address keys are written using PSLang expression based on account attributes discovered using auto discovery.

To load a discovery template:

This loads the agent with the new/modified discovery template onto the instance. You should be able to find the discovery template under Manage the system > Resources > Target systems > Discovery templates.