Encrypt Customizer Traffic in HCL Connections Component Pack

christoph.stoettner@stoeps.de (Christoph Stoettner) — Thu, 16 Oct 2025 15:00:00 +0200

Warning

The is just a proof of concept and shouldn’t be used in production! I still have some issues with redirects to the new hostname.

In the series of encrypting network traffic within HCL Connections and Component Pack:

the customizer part is missing. In a default configuration (or when you install as documented), the traffic from IHS and NGINX that is forwarded to the customizer (mw-proxy) and Ingress is unencrypted.

Encrypt IHS proxypass traffic to Component Pack

christoph.stoettner@stoeps.de (Christoph Stoettner) — Fri, 23 May 2025 21:30:00 +0200

I’m still working on encrypting all network traffic between Connections and Component Pack servers. This time I checked the Ingress-Nginx Controller - TLS/HTTPS documentation.

The default configuration for connecting IHS with Component Pack uses the plain HTTP port 32080. All traffic like /social or the Tailored Experience wizard is routed from IHS to Kubernetes on port 32080.

Our target is to encrypt the traffic on port 32443.

IBM HTTPServer on

Encrypt Customizer Traffic in HCL Connections Component Pack

Encrypt IHS proxypass traffic to Component Pack