HCL Verse client setup for SAML authentication

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 SAML authentication, the setup and re-authentication differs. During client setup, after specifying the Traveler server endpoint address, the end user is presented with the login form from the customer’s identity provider. After entering the user credentials for the identity provider, 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 identity provider login form again.