#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Safelinx should respect p12 file of each http-service. Actually it use the p12 file from the first active http-service

1. Avoid to use OpenSSL to combine many many SSL certificate from different Domains

2. Logical and clear way to handle SSL 1 http-service=1 URL subsubdomain/subdomain/domain-.com with 1 TLS certificate


3. Simplify procedure when renew and reinstall certificate


outdated cookbook: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0036211



Use case is this one:

Documentation:

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

  • Guest
  • Feb 7 2022
  • Shipped
  • Attach files
  • Admin
    Timothy Clark commented
    12 May 03:15pm

    This shipped in SafeLinx 1.3

  • Guest commented
    8 Feb 07:50am

    SAN is a solution in this use case, but the comparison with Apache which handle differents case on a more granular mode is glamourous.

    We want to switch to Safelinx from NGINX or Apache because of Nomad web, but we do not want to discover restrictions during the process. It should be as easy to configure as Apache server.