Authenticating legacy software

You can authenticate legacy software connection in the file.

The Broker uses the following record in serverConnect.conf file to authenticate legacy client connections and provide full access. The target field, with the value <BROKER>, identifies that the Broker is the sole target for authentication.

<BROKER> : <DEFAULT> : <DEFAULT> : All

Note: There are no corresponding entries in the clientConnect.conf or brokerConnect.conf.

In this configuration, the Global Console does not prompt for a username and password when connecting to the Broker. The default configuration defines a nonsecure Broker, equivalent in security to Smart Assurance software prior to version 5.0.