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.-
Download the
.exefile from the App downloads page. -
Run the
.exefile and follow the installation prompts.
-
-
MSI package (.msi)
For administrators deploying across multiple machines using scripting or GPO.-
Download the
.msifile from the Resources Downloads page. -
Deploy the
.msifile 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:
-
Download the
.pkgfile from the App Downloads page. -
Double-click the file to launch the installer.
-
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 usingsudo 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.
-
The very minimum requirements are to allow:
-
firebaseinstallations.googleapis.com on port 443 (TLS)
-
fcmregistrations.googleapis.com on port 443 (TLS)
-
fcm.googleapis.com on port 443 (TLS)
-
android.clients.google.com on port 443 (TLS)
-
mtalk.google.com on port 5228, 5229 or 5230
-
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.
-
Launch TrustBuilder Authenticator application.
-
Check “I agree” to give your consent
-
nt to the Privacy Policy.
-
Click on Activation code.
-
Enter a valid Activation code and click the validate button.
-
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:
Get pending operations: check pending operation such as authentication requests or transaction confirmation requests.
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.
-
Click on the notification to open the application.
-
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.
-
On the app’s home page, click on Pending operations.
-
If there is more than one pending operations, select the relevant one from the list.
-
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
Managing secret code
Managing trusted devices
App settings
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 |
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 |
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 |