Understanding the Configuration File

The trac_client_1.ttm file contains sets that look like this:

Copy 
<span class="Warning">:attribute (
    :gateway (
        :ext ()
        :map ()
        :default ()
)</span>
            

  • attribute - The name of the attribute on the client side. This is in trac.defaults on the client.

  • gateway - The name of the attribute on the gateway side. This is in objects.c on the Security Management Server. Look in the objects.c file to see what the defined behavior is on the gateway side. The name of the attribute is only written here if it is different from the name on the client side. If there is no value for the gateway, the name of the attribute is the same in trac.defaults and objects.c.

  • ext - If it exists, it is a hard-coded function that is defined and done on the gateway. Do not change it. This function can be done in addition to the function defined for the attribute on the client or gateway side.

  • map - Contains the correct values this attribute can have.

  • default - The value here is downloaded to the client if the gateway attribute was not found in the database. If the value is client_decide, the value is defined on the client computer, in the GUI or in the trac.defaults file on each client.

The behavior for each attribute is decided in this procedure:

  1. If the attribute is defined for the gateway in the objects.c file on the Security Management Server, that value is used.

  2. If the attribute is NOT defined for a gateway in the objects.c file, the behavior for the attribute is taken from the default value.

  3. If the default value is client_decide or blank, the behavior is taken from the client.

    • If the attribute is configured in the client GUI, it is taken from there.

    • If the attribute is not configured in the client GUI, it is taken from the trac.defaults file on each client.

Example:

Copy 
:enable_password_caching (
    :gateway ()
        :default (client_decide)
)

enable_password_caching is the name of the attribute in trac.defaults and objects.c. Search the objects.c file on the Security Management Server to see if it is defined for the gateway. 

  • If the attribute is defined for the gateway, that behavior is used.

  • If the attribute is not defined for a gateway, the default value is used. Because the default value is client_decide, the setting is taken from each client.

Configuration File Parameters

See sk75221 for the updated list of parameters for the configuration file.