How to configure TLS in Safelinx when using many http-service?

I am installing Safelinx as a reverse proxy server for http-service + Traveler.

I have a question about TLS certificate in Safelinx.

If I create 1 separate http-service for each external URL, Safelinx reply to the browser with TLS of the first http-service created.

If I want to consolidate http-service in one service (or less than my previous 4 service), it is the same.

It seems to be inline with what is written in the documentation (even if it does not make sense to me> I created a Ah-A ideas for this https://domino-ideas.hcltechsw.com/ideas/SFLX-I-34).

https://help.hcltechsw.com/safelinx/1.1/adminguide/conf_consolidationofmultipleservicesunderoneip_c.html

To enable secure connections between client devices and the DNS names that share an address and port, install a multiple-host or domain-based certificate on the SafeLinx Server.

All HTTP access services that share an address and port must also share a common SSL/TLS configuration. SSL/TLS settings include cipher restrictions, key database and stash files, and any SSL/TLS related timers and buffer sizes. The SSL settings for the first HTTP access service that registers with the SafeLinx Server are applied to all of the other services that share the address and port.

To enable secure connections between client devices and the DNS names that share an address and port, install a multiple-host or domain-based certificate on the SafeLinx Server.

How-to create a multiple-host or domain-based certificate for the SafeLinx Server ?

>p12 certificate that combine certificates for:

subsubdomain1.subdomain1.domain1.com

subsubdomain1.subdomain2.domain1.com

subsubdomain1.subdomain3.domain1.com

*.domain1.com

My guess would be to create a global pem file and to convert it.

Answer is:

Switch from using 4 different TLS certificate to ONE global SAN TLS certificate, and install it in Safelinx http-service.

SafeLinx does not currently load certificates from each file. It only uses the first activated service since all services are using the same IP address and port. Wildcard certificate is the best option but since they already have 4 separate certificates, they could combine the 4 into a single PCKS12 file and reference that file in each of the services.
There are few alternatives out there for building a pkcs12 file with multiple certificates like Java's keytool or openssl.