Getting Started

Importing the OVA image in Vmware

Ask your sales rep for a link to download the latest package of the TrustBuilder appliance. The appliance comes in the form of an OVA file named TrustBuilder-[version]-VirtualAppliance-x86_64.ova. This quickstart has been tested with version 9.1.0.

You should be able to import the OVA file into VMWare Workstation / Player (or even VirtualBox). Choose a name for the virtual machine and the final location of the  virtual machine. (Alternatively, unzip the OVA file and open the unzipped file TrustBuilder-[version]-VirtualAppliance-x86_64.ovf from within VMWare.)

Once the import succeeds you can delete the OVA file (and the unzipped files).

Set the appliance password

When logging in to the VMWare console, you will be first asked to select a keyboard layout. (You can change the layout later on.)

Now login with user trustbuilder and password trustbuilder. You will be asked to change the password. Enter and confirm the new password. (The appliance may complain if you use a trivial password.)

Note. While you can use the VMWare console to configure TrustBuilder, we recommend using an external SSH client of your choice to connect to the virtual machine once you know the IP address of the appliance.

Determine the IP address of TrustBuilder

Determine the ip address of the appliance by typing: ip address.

This should tell you the IP address assigned to the virtual machine by DHCP.

  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet scope host lo
         valid_lft forever preferred_lft forever
  2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
      link/ether 00:0c:29:18:4e:ec brd ff:ff:ff:ff:ff:ff
      inet brd scope global dynamic eth0
         valid_lft 1509sec preferred_lft 1509sec

Change the console keyboard

To permanently change the keyboard mapping run the localctl command.

For instance, localctlset-keymap us instructs the appliance to use the US keyboard.

Set the environment

You can install the VMware tools by issuing the command sudo yum install open-vm-tools. (Depending on the appliance version these may come pre-installed.)

The quickstart supposes that you will be using TrustBuilder version 9.2.0. Some of the screens may differ somewhat if you are using another version of TrustBuilder. If the OVA file you started with has a lower version number, like 9.1.0, you can instruct the appliance to upgrade from 9.1.0 to 9.2.0.

Go to the following configuration directory: cd /opt/trustbuilder/appliance/config. This directory contains important configuration files, such as the environment and appliance configuration. 

Enter the command:  sudo vi environment.yml to edit the major version in the environment.yml file as follows:

- hosts: localhost
  become: yes
    - { role: environment,
        tb_repo: "production",
        tb_version: "9",
        tb_version_major: "2",
        tb_version_minor: "0",
        update_packages: false

Then execute the command ansible-playbook environment.yml to propagate the changes.

Update the appliance libraries

To retrieve the latest builds for the current environment issue the following command:  sudo yum update .

The output will look something like this:

Loaded plugins: fastestmirror
Determining fastest mirrors
centos-7-extras                                          | 2.9 kB     00:00     
centos-7-os                                              | 2.9 kB     00:00     
centos-7-updates                                         | 2.9 kB     00:00     
mariadb                                                  | 2.9 kB     00:00     
tb-appliance-9.2.0-production                           | 2.9 kB     00:00     
tb8-appliance-custom                                     | 2.9 kB     00:00     
(1/6): mariadb/primary_db                                  |  21 kB   00:00     
(2/6): tb8-appliance-custom/primary_db                     |  54 kB   00:00     
(3/6): tb-appliance-9.2.0-production/primary_db           | 275 kB   00:00     
(4/6): centos-7-extras/primary_db                          | 7.6 MB   00:02     
(5/6): centos-7-updates/primary_db                         | 9.3 MB   00:04     
(6/6): centos-7-os/primary_db                                         | 8.0 MB  00:00:05     
Resolving Dependencies
--> Running transaction check
---> Package ansible.noarch 0:2.5.2-1.el7 will be updated
---> Package ansible.noarch 0:2.5.5-1.el7 will be an update
---> Package kernel.x86_64 0:3.10.0-862.3.3.el7 will be installed
---> Package kernel-tools.x86_64 0:3.10.0-862.3.2.el7 will be updated
---> Package kernel-tools.x86_64 0:3.10.0-862.3.3.el7 will be an update
---> Package kernel-tools-libs.x86_64 0:3.10.0-862.3.2.el7 will be updated
---> Package kernel-tools-libs.x86_64 0:3.10.0-862.3.3.el7 will be an update
---> Package linux-firmware.noarch 0:20180220-62.git6d51311.el7 will be updated
---> Package linux-firmware.noarch 0:20180220-62.2.git6d51311.el7_5 will be an update
---> Package nodejs.x86_64 1:6.14.0-1.el7 will be updated
---> Package nodejs.x86_64 1:6.14.2-1.el7 will be an update
---> Package npm.x86_64 1:3.10.10- will be updated
---> Package npm.x86_64 1:3.10.10- will be an update
---> Package python-perf.x86_64 0:3.10.0-862.3.2.el7 will be updated
---> Package python-perf.x86_64 0:3.10.0-862.3.3.el7 will be an update
---> Package trustbuilder-appliance.noarch 0:9.1.0-433 will be updated
---> Package trustbuilder-appliance.noarch 0:9.2.0-73 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

 Package                Arch   Version                          Repository                      Size
 kernel                 x86_64 3.10.0-862.3.3.el7               centos-7-updates                46 M
 ansible                noarch 2.5.5-1.el7                      centos-7-extras                9.0 M
 kernel-tools           x86_64 3.10.0-862.3.3.el7               centos-7-updates               6.2 M
 kernel-tools-libs      x86_64 3.10.0-862.3.3.el7               centos-7-updates               6.2 M
 linux-firmware         noarch 20180220-62.2.git6d51311.el7_5   centos-7-updates                57 M
 nodejs                 x86_64 1:6.14.2-1.el7                   centos-7-extras                4.7 M
 npm                    x86_64 1:3.10.10-         centos-7-extras                2.5 M
 python-perf            x86_64 3.10.0-862.3.3.el7               centos-7-updates               6.2 M
 trustbuilder-appliance noarch 9.2.0-73                         tb-appliance-9.2.0-production  91 k

Transaction Summary
Install  1 Package
Upgrade  8 Packages

Total download size: 138 M
Is this ok [y/d/N]: 

Enter y to confirm the update. (This may take a few minutes.)

Configure IDHub

The TrustBuilder appliance comes with several example configurations located in the /opt/trustbuilder/appliance/config directory. We will use the  singlemachine.example.yml configuration, which specifies a single-node installation of the appliance.

Change the current directory to /opt/trustbuilder/appliance/config.

Execute the command: ansible-playbook singlemachine.example.yml. (This will take several minutes.)

You are now ready to finish the TrustBuilder installation by pointing a web browser to:


Login with username Administrator and password ChangeAfterInstall. You will be prompted to select and confirm a new password.

You will then be prompted to generate keys and certificates.

Then you will be asked if you want to reset the page settings to their default templates. Since this is a new installation, a reset is not needed. Select the Skip option instead.

The installation is now completed. Clicking the Admin Portal button brings up the login screen of the TrustBuilder administration application.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.