Linda
The rule for a WCC in a cluster (sharing the same DB) is that they all need to use the same protocol http or https.
We solved this by putting the required WCCs behind a load-balance and did SSL offload on the load-balancer. All the WCCs were talking http and then for the ones that had traffic across an "untrusted" network we used a LB (either HAproxy or BIG-IP depending on the availability). Don't forget session "stickiness" in the LB, but it all works very well for us.
Regards, Andrew
------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------
Original Message:
Sent: 04-08-2021 12:28 PM
From: Linda Williams
Subject: WCC http to https
But you can't do that if you have multiple wcc's correct? Did that change in 12.0?
Original Message:
Sent: 03-24-2021 04:53 PM
From: Michael Woods
Subject: WCC http to https
Hi Dale,
I don't know the answer about the sniffer, but if you want to change from http to https, run the wcc_config.sh script.
There is an ssl=on|off that will change it. It does require a recycle to take effect. You may want to switch the port to a 'ssl' one as well, like 8080->8443.
Regards,
Mike
Original Message:
Sent: 03-24-2021 02:33 PM
From: Dale Klaves
Subject: WCC http to https
Is this true about WCC? Without HTTPS someone could potentially sniff the traffic and discover the persons credentials easily.
We are currently using LDAPS in EEM.
Is there a document that shows how to change WCC to use https instead of http, or is a reinstall required?