HCL Verse client setup for TOTP authentication

This topic describes the setup process for HCL Verse clients with TOTP authentication.

Note: A prerequisite for configuring an HCL Verse Client for TOTP is the user setup for Multi-factor authentication (MFA). The user must configure a TOTP application (desktop or mobile) associated with their Domino user ID. For more information, see How users setup TOTP in the HCL Domino documentation.

In a typical HCL Traveler environment configured for Basic authentication, mobile clients are configured with the Traveler server endpoint. The user’s http login username and password are required to complete the setup. After setup, the mobile clients handle any authentication issue from the service without involving user interaction (with a few exceptions, such as password expiration).

In an environment configured for TOTP authentication, the setup and re-authentication differs. During client setup, after specifying the Traveler server endpoint address, the end user is presented with the TOTP login form. The user enters the Domino user id and http password and the TOTP code from the configured TOTP application.
Note: The TOTP setup (described in How users setup TOTP) cannot be completed from within the HCL Verse client’s setup process. Once authenticated, the client setup proceeds through the standard initial configuration flow for the HCL Verse applications. However, the client does not capture the user’s login credentials in the account settings. On any subsequent authentication issue, the user is presented with the TOTP login form again.