Opening a platform connection to a host

A platform (host) connection differs from a station connection in that when connected to a platform, Workbench communicates (as a client) to the host’s platform daemon, niagarad (daemon), a server process. Unlike a station connection that uses the Fox/Foxs protocol, a client platform connection ordinarily requires full Workbench, meaning it is unavailable using a standard Web browser or Web Launcher. Using a browser, a Supervisor station can connect to a remote platform through its ProvisioningService.

The platform (PC localhost or controller) has been physically installed and connected. The host is licensed with the license server.
  1. Right-click My Host in the Nav tree and click Open Platform.
    The Connect window opens with the name of your computer or remote controller as the Host name.

    It is possible to make this type of secure TLS (Transport Layer Security), encrypted platform connection to any Niagara 4 host, provided it is properly configured.

    Note: For best security, always use TLS. In Workbench, the default Open Platform and Open Station (Foxs) commands assume a secure connection. To make an unencrypted connection you must change the connection Type first.

    If you received an e-mail with the License Key for a host, a pending unbound license already exists on the licensing server.

  2. If prompted, enter the license key along with the part number to activate the host’s license, and make it immediately available.
  3. To accept the host name, click OK.
    The Authentication window opens.

    Once the platform is connected, the available platform functions are identical—regardless of connection method.

  4. Do one of the following:
    • If connecting to a controller, enter the credentials (user name and password) required by the controller.
    • If connecting to your PC localhost, enter the credentials you use to log in to your computer.
    As a platform client, you log in to either type of host using host level credentials for authentication. This means a user account and password separate from any station user account. Consider these credentials the highest level access to that specific host.
    CAUTION: A new controller ships with default platform credentials that are widely known—and if left unchanged the controller is extremely susceptible to being hacked. Starting with the Niagara 4 startup commissioning process, you must change the default user name and password to something known only to your company and/or customers.
  5. Enable Remember these credentials and click OK
    A new controller ships with default platform credentials that are widely known—and if left unchanged leave the controller extremely susceptible to being hacked. If Workbench detects factory default credentials when connecting to a remote platform it launches the Change Platform Defaults Wizard (shown here) which forces you to change the factory defaults prior to completing your platform connection.

    If platform defaults are not detected the platform connection completes. If platform defaults are detected then proceed with the following substeps.

    Note: If the Workbench FIPS property Show FIPS Options is set to true certain FIPS options become visible in this window. If selected, the framework enforces FIPS-strength password requirements.
    1. In the Change Platform Defaults Wizard, click Next to step through creating a system passphrase, creating a new platform account, and removing the default platform account, as shown below.

    2. Click Finish to complete these changes.
    The system completes making the connection between the host and Workbench, and displays the Nav Container View.
    Figure 1. Platform functions listed in platform’s Nav Container View


    The platform-connection session icon appears in the Nav tree with a small padlock to indicate the connection type, that is: either for secure TLS encryption, or for an unencrypted connection.

    Each platform function has its own Workbench view (plugin), which you access by double-clicking the view name. Most of the same platform views exist for both a platform connection to a controller and a Supervisor, with these exceptions:

    • If you open a local platform connection at your computer, some platform views appear to be missing, for example the Distribution File Installer and Software Manager are not in the list. These views have no application when working at your computer—instead, you simply use Windows Explorer.

    • A few of the platform views differ depending on platform type.

  6. To view information about the current session, right-click Platform > Session Info.
    This same information is available when right-clicking Station > Session Info


    This is an example of this client session information from a secure (TLS) platform connection. The identity of the (server) has been verified by a signed certificate, and all data sent over this connection are encrypted.