HCL SafeLinx, SAML and lesson learned

Last week I configured a HCL SafeLinx Server for HCL Nomad Web with SAML authentication and this was working in a very short time.

Afterwards the customer asked me if it would be possible to use HCL SafeLinx also for webmail access – of course it does. So I configured a HTTP service and also enabled SAML authentication.

During the tests HCL Nomad Web was working fine but when trying to open the configured link “https://extmail.company.com” the SAML authentication opened, was done and then I was redirected to “https://nomad.company.com”. I first thought about some issues with DNS entries but no modification changed.

Today I had a remote session with HCL support ( thanks for the really helpful hints ) and received the information that by now you only can configure one service on HCL SafeLinx for SAML authentication !! After switching the SAML authentication to the basic authentication also the webmail access was working.

There’s an idea on AHA where you can vote for the enhancement to have SAML authentication available on multiple configured services: https://domino-ideas.hcltechsw.com/ideas/SFLX-I-39

Leave a comment