The Connect/Open Platform window opens.

The daemon runs automatically when the controller is powered up. As shown above, the connection defaults to a secure Type Platform TLS Connection. After initial platform configuration you will always access the platform using this type of secure connection. (TLS stands for Transport Layer Security.)

For this initial installation purposes only, the system requires a regular platform connection.

The Authentication window opens and prompts you for your credentials.

The factory default Username is tridium. The factory default Password is niagara.

The platform detects the default credentials and opens the Change Platform Defaults Wizard.

The system will not let you continue with default credentials. User names and passwords form the front-line of defense against unauthorized system access.

The passphrase protects the platform’s file system, encrypting the HSQL database when you create a station copy. The Distribution File Installer requires the system passphrase to restore a backup .dist file. The Station Copier requires the same system passphrase to transfer a local file.

Best practice: Use the same Passphrase for your Supervisor and controller platforms.

The system completes making the connection between the host and Workbench, and displays the Nav Container View

A secure TLS connection is the default. This protocol provides data encryption and server authentication to prevent malicious hacks into the system.

The Identify Verification window opens with an error message.The error message indicates that the controller’s server certificate is self-signed. As such, it can encrypt data communication, but it cannot authenticate the server (the controller) to its client ( Workbench). This is because none of the root certificates in the Workbench Trust Store recognize this certificate. Since you know that the controller is a valid server you can accept the self-signed certificate temporarily so as to continue with the login.