TrustBuilder Authenticator - version 7

Authenticator 7 is currently in beta for Android and iOS. Fill-out this form if you wish to participate.

The 7th version of TrustBuilder Authenticator is a major release, offering a completely redesigned user experience. It complies with the WCAG 2.1 Level AA accessibility standards, ensuring greater accessibility for all users.

New: see at the end of this page for 7.1 updates

Upgrade from previous versions

User will get TrustBuilder Authenticator 7.0 as an upgrade from previous versions numbered 6.x. The upgrades from iOS and Android will be transparent as usual, as well as the upgrades from the Windows Store when available.

New home page

The home page is more simple, and now offers direct access to the most frequent authentication use cases. The user can directly check pending operations, scan a QR code to authenticate (when activated by the administrator) or generate an OTP.

Other non-frequent actions such as managing devices have been moved to the menus.

New application settings menu

All the settings that are local to the application have been centralized in a simple settings menu accessible by clicking on the in the upper left corner.

This menu allows the user to change the language, and the mode: Light, Dark or System (new). The user can also find information that is useful in case of calling the helpdesk, such as the app version, and mandatory legal information.

New account menu

By clicking on the in the upper right corner, the user can access the Account menu. This standard account menu allows to manage the current account, to easily switch between accounts or add a new account.

Manage my account

The Manage my account page gives a centralized access to all topics related to the account, such as the management of the Security settings (PIN, biometric authentication), and some features that are subject to activation by the administrator such as the management of the trusted devices or the recovery email.

The management of the biometric authentication has been improved, it is now easier to activate biometric authentication in the security menu.

Accept/Reject Page

The Accept/Reject page appears in the authentication scenario to explicitly ask the user to confirm or reject an ongoing authentication request. The page was present in Authenticator 6 only for biometric authentication (fingerprint or facial recognition), in order to increase the security by avoiding users to inadvertently accept an unsolicited notification.

This page scope has been extended to all authentication scenarios, as it proved to be efficient as a security measure to protect against unsolicited authencation requests. The explicit question will lead the users to reject the operation if they did not initiate it.

Accessibility

Authenticator 7.0 complies with the WCAG 2.1 Level AA accessibility standards (Web Content Accessibility Guidelines), ensuring greater accessibility for all users. This regulation will become mandatory in the public sector and banks in 2025 and may become also mandatory for all companies with a turnover over 250m Euro.

This means that the application has been designed to be used with screen readers such as VoiceOver on iOS and TalkBack on Android. Users may also adjust the size of the text, use the app in landscape mode for better readability or use a keyboard to navigate through the app.

Image Library

For security reasons Authenticator 7 is protected agains screen shots. However if you wish to update your internal documentation for your end-users, you can find screen shots of all pages in English and French in our GitHub image library.

Version 7.1 update

Improvements vs 7.0

• Improvement of the pinpad interface

• Wording improvement in French (code PIN)

• Updated the behavior when the user declines an authentication request

• [Android] Updated the action buttons after an authentication

• Bug fixes

• Costmetic updates

Known issues

• Notification: no redirection to the authentication request page when “Enter PIN” page is open

• Multi-service account: when a user has two account, in a service with PIN and another without, generating an OTP in the PIN service leads to a connection error

• Android: when the app is open, clicking on a notification does not lead to the right page

• Android: when scanning a QR code on Android 15, the button “Enter an activation code” is not present