TrustBuilder Safe-T

TrustBuilder Authenticator - Desktop app

Installing TrustBuilder Authenticator

TrustBuilder Authenticator Desktop is compatible with the following operating systems:

TrustBuilder Authenticator 7 for Windows is available as:

  • Executable file (.exe)
    For individual users downloading manually from the App Downloads page.

    1. Download the .exe file from the App downloads page.

    2. Run the .exe file and follow the installation prompts.

  • MSI package (.msi)
    For administrators deploying across multiple machines using scripting or GPO.

    1. Download the .msi file from the Resources Downloads page.

    2. Deploy the .msi file using administrative tools like GPO, SCCM, or Intune for centralized distribution.

  • Windows Store
    Simplified installation and update process.
    Download and install from the Windows Store.

Proxy

TrustBuilder Authenticator for Windows will use the PROXY - HTTP_PROXY - HTTPS_PROXY environment variables when they are defined.

To ignore any proxy settings, you can add the environment variable NO_PROXY with any value.

Log file location

Available from version 7.4.

The log files are stored in the following directories, depending on the installation method:

  • .exe → C:\Users\{user}\AppData\Roaming\Authenticator 6\logs

  • .msi → C:\Users\{user}\AppData\Roaming\Authenticator 6\logs

  • Windows Store → C:\Users\{user}\AppData\Local\Packages\inWebo.inWeboAuthenticator6_w5tsbdy5jdsxj\LocalCache\Roaming\Authenticator 6\logs

These logs provide insights into the application's operations and can be used for troubleshooting if needed.

TrustBuilder Authenticator is available for MacOS as a .pkg file:

  1. Download the .pkg file from the App Downloads page.

  2. Double-click the file to launch the installer.

  3. Follow the installer instructions to complete the installation.

TrustBuilder Authenticator for Linux is delivered in AppImage format. This format is compatible with a wide range of 64-bits Linux distributions, however TrustBuilder is using the latest version of Ubuntu LTS as a reference platform. The reference platform is used by TrustBuilder as follows:

  • The app is validated by TrustBuilder on the reference platform

  • If an issue is reported, TrustBuilder will use the reference platform to reproduce and fix the issue

  • The AppImage format will ensure compatibility with other Linux distributions

Download TrustBuilder Authenticator app for Linux

Prerequisites

  • The Keyring package is mandatory as it is used to store the user secrets in the user keychain.
    If the package is not present, you can install it using sudo apt install gnome-keyring.
    When launching the application, the Keyring must be unlocked by the user.

  • AppImages require FUSE version 2 to run. Depending on the Linux distribution you are using, you may have to install it. You can install it using sudo apt install libfuse2. For more information see FUSE.

Network prerequisites for Notifications

TrustBuilder Authenticator uses Google’s Firebase Cloud Messaging (FCM) services to register devices and deliver notifications to these devices. If you are using notifications, and if your organization uses a firewall to restrict traffic to or from the Internet, you need to configure it to allow mobile or desktop devices to connect with FCM.

info The IP address used by Authenticator for the notification mechanism belongs to block ASN 15169 (Google).

Notes

  • TrustBuilder Authenticator maintains an open session with FCM to receive notifications.

  • Notifications do not contain sensitive or secure data.

  • They are identical for both mobile and desktop applications.

  • Notifications improve the user experience. Users can always retrieve pending authentication requests manually in the Authenticator app.

Related documentation: Our recommendation is to apply the official Firebase network prerequisites by Google. This is documented here and may vary over time: https://firebase.google.com/docs/cloud-messaging/concept-options#messaging-ports-and-your-firewall.

First app launch

To get started with TrustBuilder Authenticator app, you should first add a new account.

Prerequisite: an activation code or link.

  1. Launch TrustBuilder Authenticator application.

  2. Check “I agree” to give your consent

  3. nt to the Privacy Policy.

  4. Click on Activation code.

  5. Enter a valid Activation code and click the validate button.

  6. Define or enter your secret code.

You have successfully added your account. This device is now registered as an authentication method. You can use it for authentication.

Overview

From the home page you can perform several actions:

The Authenticator app for Bob White at MyCompany shows pending operations.

Get pending operations: check pending operation such as authentication requests or transaction confirmation requests.

image-20240729-095159.png (user icon): manage your account (Secret code, authentication methods) or add a new account.

image-20240729-095353.png (cogwheel icon): see and configure your application (language, theme, app version).

Authenticate with the app

There are several ways to authenticate using the TrustBuilder Authenticator application. Depending on how your service settings are configured, you may be able to authenticate using the following methods:

Receive a push notification

You will receive a push notification trough TrustBuilder Authenticator app. You should then approve or reject the pending operation. Each approval operation is protected by secret code.

  1. Click on the notification to open the application.

    Authentication request 7 desktop.gif
  2. Accept or reject the authentication request.
    Enter secret code.

Retrieve pending operations

This feature allows the app to fetch any active pending operations when no notifications are available.

  1. On the app’s home page, click on Pending operations.

  2. If there is more than one pending operations, select the relevant one from the list.

  3. Approve or reject the operation.
    Enter your secret code.

Accept or Reject an authentication request

When receiving an authentication request, the app will ask 'Did you initiate this authentication?'.
There are two options:

  • Yes, it's me – Confirm your identity by entering your authentication factor to proceed.

  • No – In this case, you can choose one of the following actions:

    • Ignore this authentication: the request remains active. It can still be approved from another device.

    • Reject this authentication: the request is canceled and cannot be approved anymore. This option is useful if you suspect the request is malicious.

Configuration

Managing accounts

Adding a new account
  • Prerequisite: you should have a valid activation code for the account you wish to add.

  1. Click on the user icon in the top-right corner.

  2. Click on Add an account.

  3. Enter a valid Activation code to add a new account on this device.

Your account is successfully added to TrustBuilder Authenticator app on the current device.

Switching between accounts

If you registered for more than one service, you may need to switch from one account to another.

  1. Click on the user icon on the top right corner.

  2. Click on the account you wish to use.

Removing account from the app

Removing your account from the application in the current device means that the account and all its data will be removed from the current trusted device.

  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Remove this account.

  3. Click on Remove this account then on Yes, remove to confirm your choice.

Your account has successfully been removed from this device.

Displaying account information

To display your account information:

  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Account information.

Your account and some context information are displayed. This could be useful for the helpdesk team when troubleshooting any issue the user might have.

Account information

  • Account :

    • Login → current user’s login

  • Support information:

    • Device alias → the alias of the current device

    • Notification reception → the status of the notification registration

    • Platform version → this information will be useful during platform upgrades.
      Default is 1 for the current platform

Setting account recovery information

TrustBuilder requires a valid email address in case your account gets locked or your devices are lost. This email may be used for identification purposes when requesting account restoration via http://myinwebo.com. It may also be used to receive a restore code to unlock your trusted authentication devices.

To set or update your account recovery email:

  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Recovery email.

    • If the email address is verified, you can update it.

    • If the email address is not verified, you can:

      • Click Resend email to receive a verification email. Follow the instructions to verify your email address.

      • Click Modify email address to change the registered email address.

Managing secret code

Modifying your secret code
  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Security.

  3. In secret code section, click on Modify.

  4. Enter your current secret code and define your new secret code.

  5. Click on Modify my secret code to save.

Your new secret code has been successfully modified.

Resetting your secret code

Prerequisite: a Reset code

  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Security.

  3. In secret code section, click on I forgot my secret code.

  4. Enter your reset code.
    If you don’t have a reset code, click on “I don’t have a reset code” and follow the instructions.

  5. Click on Verify.

  6. Define your new secret code.

  7. Click on Define my new secret code to save.

Your new secret code has been successfully reset.

Managing trusted devices

Adding a new trusted device

You can generate an activation code to be used to add a new trusted device to your account.

  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Trusted devices.

  3. Click on + Add a trusted device.

Ann activation code will be displayed. Use either one on the new trusted device to add it to your account.

Renaming a trusted device
  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Trusted devices.

  3. In your trusted devices list, click on the trusted device to be renamed.

  4. Click on the pen icon in the top-right corner.

  5. Rename the trusted device and click on Update to save.

The selected trusted device has been successfully renamed.

Lock a trusted device

You can lock any trusted devices registered in your account, except the one you are currently using.

  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Trusted devices.

  3. In your trusted devices list, click on the trusted device you want to lock.

  4. Click on Lock this trusted device, then confirm by clicking Yes, lock.

The selected trusted device has been successfully locked.

Deleting a trusted device

You can delete any trusted devices registered in your account, except the one you are currently using.

  1. Click on the user icon in the top-right corner.

  2. Go to Manage my account > Trusted devices.

  3. In your trusted devices list, click on the trusted device you want to delete.

  4. Click on Delete this trusted device, then confirm by clicking Yes, delete.

The selected trusted device has been successfully deleted.

App settings

Setting the app's language
  1. Click on the cogwheel icon in the top-left corner to access the application settings.

  2. Click on Language.

  3. Select your language.

The application switches to selected language.

The application's default language is determined by the phone's system language. If the system language is not supported, the application will default to English.

The following languages are supported by the application:

  • English

  • Deutsch (German)

  • Nederlands (Dutch)

  • Español (Spanish)

  • Français (French)

  • Italiano (Italian)

  • 中文 (Chinese)

Setting light/dark mode
  1. Click on the cogwheel icon in the top-left corner to access the application settings.

  2. Click on Mode.

  3. Select a mode:

    • Light → your application will switch to light mode.

    • Dark → your application will switch to dark mode.

    • System → the mode will follow your device’s settings.

The application switches to the selected mode.

The application's default mode is determined by the phone's system mode.

App version

To get your application version, click on the cogwheel icon in the top-left corner. In the About section, you will see the “Application version” parameter.

Accessibility Features

TrustBuilder Authenticator 7th version is designed to be accessible for users with various disabilities, in line with WCAG 2.1 guidelines. Below are the key accessibility features available in the app:

  • Screen Reader compatibility
    TrustBuilder Authenticator is compatible with VoiceOver (macOS) and Narrator (Windows). Users can navigate the app's menus, input fields, and authentication processes. Just turn on the screen reader on your device, and the app will provide voice instructions.

  • Keyboard navigation
    Users can navigate the app using keyboard shortcuts. Use the “Tab key” to move between elements and “Enter” to select. The app follows a logical tab order to ensure seamless navigation.

  • Text Size and Contrast
    TrustBuilder Authenticator app supports dynamic text scaling. Users can adjust the font size in their device settings and the app will automatically update to reflect the changes. The app also supports the high-contrast text mode, which changes the text to black or white to improve visibility against the background.

Support policy per Operating System

  • Minimum requirements are the minimum version on which the Authenticator application can be installed. Users currently running an earlier version of the operating system cannot upgrade to the current version of Authenticator. While the previously installed version of Authenticator may still function, it will no longer fall within TrustBuilder’s recommended usage or support scope.

  • Supported OS version. For security reasons we highly recommend using an operating system that is supported and that benefits from security patches. In case of a reported issue, TrustBuilder will reproduce it on a supported OS version.

You will find the details of minimum requirements and supported version by operating system in the following table:

Operating System

Minimum requirements

Supported Versions

Windows

Windows 10

Windows 10 22H2 until Oct 14, 2025

Windows 11

macOS

macOS 13

macOS 13, 14, 15

Linux

supported by appimage

Latest Ubuntu LTS

For more details please check:

Authenticator version lifecycle

The current version is the most recent version of the application that is available for download. It is actively maintained and updated at least twice a year, it includes the latest features and security patches, and is recommended for all users as the primary version to install and use. If users have chosen the stores to install, it is recommended to turn auto-update ON.

For older versions, TrustBuilder will provide support for versions released within the past two years. In the event of a blocking issue, our investigation may lead to one of two outcomes: either the issue has already been resolved in the latest version, or it will be addressed in the next release. In both cases, upgrading to the latest version (current version) will be required to benefit from the fix.

Versions older than two years are deprecated. TrustBuilder does not accept support calls on these versions. Usage is discouraged as they pose potential risks (e.g., security vulnerabilities or reduced functionality). Sooner or later they will experience compatibility issues with either the environment or the platform and will no longer be functional. Also the direct upgrade to the current version is not guaranteed.

Summary table

Version

Support provided

Updates

Recommendation

Current Version

Support and updates

Yes

Regularly check for new version.

If available, turn auto-update ON.

Less than 2 years

Support calls

Upgrade to current is possible.

No

Upgrade to current version is recommended

Older than 2 years

Deprecated. No support calls.

No

 

Windows Version Details

Authenticator Version

OS

Release date

End of support (2 years)

Status

7.12.1

Windows (store only)

22-Oct--2026

22-Oct-2028

Current

7.12.1

Windows

20-Oct-2026

20-Oct-2028

Current

7.11.2

Windows

4-May-2026

4-May-2028

Support calls, no updates

7.10.2

Windows (store only)

2-Mar-2026

2-Mar-2028

Support calls, no updates

7.10.2

Windows

26-Feb-2026

26-Feb-2028

Support calls, no updates

7.9

Windows (store only)

8-Dec-2025

8-Dec-2027

Support calls, no updates

7.9

Windows

1-Dec-2025

1-Dec-2027

Support calls, no updates

7.7

Windows (store only)

08-Sep-2025

08-Sep-2027

Support calls, no updates

7.7

Windows

27-Aug-2025

27-Aug-2027

Support calls, no updates

7.6

Windows

28-Jul-2025

28-Jul-2027

Support calls, no updates

7.5

Windows (store only)

12-Jun-2025

12-Jun-2027

Support calls, no updates

7.4

Windows

28-Mar-2025

28-Mar-2027

Support calls, no updates

Earlier versions

Authenticator Version

OS

Release date

End of support (2 years)

Status

6.38

Windows

11-Sep-2024

11-Sep-2026

Deprecated

6.32.2

Windows

09-Nov-2023

09-Nov-2025

Deprecated

6.31

Windows

21-Sep-2023

21-Sep-2025

Deprecated

6.30

Windows

26-Jul-2023

26-Jul-2025

Deprecated

6.27

Windows

19-Apr-2023

19-Apr-2025

Deprecated

6.25.1

Windows

22-Feb-2023

22-Feb-2025

Deprecated

6.24.2

Windows

13-Feb-2023

13-Feb-2025

Deprecated

6.22

Windows

10-Oct-2022

10-Oct-2024

Deprecated

6.20

Windows

28-Jun-2022

28-Jun-2024

Deprecated

6.19.3

Windows

01-Apr-2022

01-Apr-2024

Deprecated

6.18

Windows

14-Jan-2022

14-Jan-2024

Deprecated

6.14.5

Windows

20-Sep-2021

20-Sep-2023

Deprecated

6.14.3

Windows

12-Jul-2021

12-Jul-2023

Deprecated

6.12.3

Windows

20-Jan-2021

20-Jan-2023

Deprecated

6.14

Windows

01-Jul-2021

01-Jul-2023

Deprecated

6.8.4

Windows

15-Jan-2020

15-Jan-2022

Deprecated

MacOS Version Details

Authenticator Version

OS

Release date

End of support (2 years)

Status

7.12.1

macOS

20-Oct-2026

20-Oct-2028

Current

7.12

macOS

28-Sep-2026

28-Sep-2028

Support calls, no updates

7.11.2

macOS

4-May-2026

4-May-2028

Support calls, no updates

7.10.2

macOS

9-Mar-2026

9-Mar-2028

Support calls, no updates

7.9

macOS

8-Dec-2025

8-Dec-2027

Support calls, no updates

7.7.1

macOS

11-Sep-2025

11-Sep-2027

Support calls, no updates

7.5.3

macOS

21-May-2025

21-May-2027

Support calls, no updates

Earlier versions

Authenticator Version

OS

Release date

End of support (2 years)

Status

 6.38

macOS

11-Sep-2024

11-Sep-2026

Deprecated

6.37

macOS

13-Jun-2024

13-Jun-2026

Deprecated

6.32.2

macOS

09-Nov-2023

09-Nov-2025

Deprecated

6.30

macOS

26-Jul-2023

26-Jul-2025

Deprecated

6.22

macOS

10-Oct-2022

10-Oct-2024

Deprecated

6.19

macOS

21-Mar-2022

21-Mar-2024

Deprecated

Linux Version Details

Authenticator Version

OS

Release date

End of support (2 years)

Status

7.12.1

Linux

20-Oct-2026

20-Oct-2028

Current

7.11.2

Linux

4-May-2026

4-May-2028

Support calls, no updates

7.10.1

Linux

26-Feb-2026

26-Feb-2028

Support calls, no updates

7.9

Linux

8-Dec-2025

8-Dec-2027

Support calls, no updates

7.7.1

Linux

11-Sep-2025

11-Sep-2027

Support calls, no updates

7.6.1

Linux

30-Jul-2025

30-Jul-2027

Support calls, no updates

7.4.1

Linux

07-Apr-2025

07-Apr-2027

Support calls, no updates

Earlier versions

Authenticator Version

OS

Release date

End of support (2 years)

Status

 6.38

Linux

11-Sep-2024

11-Sep-2026

Deprecated

6.32

Linux

11-Oct, 2023

11-Oct, 2025

Deprecated