Configuring the HCL Traveler server for OIDC authentication

OIDC authentication uses HTTP Bearer authentication. Because Bearer authentication operates via HTTP headers, it does not trigger the session override rules associated with forms-based logins that Traveler requires for HTTP Basic authentication.

Note: Domino HTTP supports multiple authentication types for the same internet site, so it is possible to use Basic and Bearer authentication at the same time.

Traveler server setup

The HCL Traveler server(s) should be configured prior to enabling OIDC authentication. This allows validation that HCL Traveler is functioning prior to making any changes for OIDC authentication.

Preparing for OIDC authentication

Read the following notes, then complete the required steps in the HCL Domino Administration guide for Preparing for OIDC authentication:
  • The Identity Provider (IdP) Catalog needs to be replicated to any HCL Traveler server participating in the OIDC federated authentication.
  • ID Vault setup is not required as part of enabling OIDC support for the HCL Verse mobile clients. If ID Vault setup is needed for other web clients, make sure that the vault security policy setting document is enabled to Allow password authentication to the ID vault. This allows HCL Verse mobile clients to continue using password authentication to access the notes id file when working with encrypted mail.
  • Mobile clients cannot participate in Windows Integrated Authentication (WIA).
  • Traveler server testing - after making the changes in this section, validate that you can still access the Traveler endpoint.

OIDC setup

OIDC authentication setup for the HCL Verse mobile clients follows the steps defined in the HCL Domino Administration guide for Configuring Verse Mobile with OIDC login. This topic identifies Traveler server specific setup information.