As of now, the current HCL Traveler documentation states that SAML Authentication for HCL Traveler is not supported when using HCL SafeLinx as a proxy. Please add SAML support for HCL Traveler when using HCL SafeLinx as a proxy server.
In many environments, HCL SafeLinx is only used because it offers:
A secure way to connect to the HCL Traveler servers over the internet.
Load Balancer features needed for the usage of HCL Traveler High Availability Pool.
A pre-authentication mechanism (allowing to authenticate users before they can actually access the HCL Traveler resources).
This would expand the functionality of HCL SafeLinx and allow using SAML authentication with HCL Traveler without modifying the current environment (going for a different proxy altogether) …
Ideally, HCL SafeLinx would function as the SAML SP (Service Provider) and authenticate the users before they can access the data and not simply passthrough the connection to the Domino Server, which then has to take the role of the SP.