Currently HCL SafeLinx is not supported when used as a proxy server when SAML Authentication comes into play. Please add SAML support for HCL SafeLinx when it is being used as a proxy server for other HCL products from the Digital Solutions portfolio.
In many environments, HCL SafeLinx is only used because it offers:
A secure way to connect to the HCL services over the internet.
A pre-authentication mechanism (allowing to authenticate users before they access the resources in the backend, like mail while using Verse on-Premises).
Load Balancer features needed for the usage of HCL Traveler High Availability Pool.
This would expand the functionality of HCL SafeLinx and allow using SAML authentication across the HCL Digital Solutions portfolio without modifying the current environment (going for a different proxy or security appliance 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 and/or Sametime servers, which then must take the role of the SP.