We use a hardware load balancer (F5 switch) that is configured to encrypt/decrypt traffic as described on page 36 of the Installation and Administration Guide. We do not use an external web server. As noted on page 36, "Setting up your system this way can improve its performance."
We have been using our hardware load balancer to encrypt/decrypt https traffic from the users without an external web server for a couple of years. The admin guide does make a point of stating that "To use HTTPS, you must also use an external Web server." It follows this, though, with the statement, "Many hardware load balancers support handling HTTPS and forwarding plain HTTP. In this case, the hardware load balancer handles the encryption and decryption of requests, and the nodes perform other tasks."
Figure 2-3 shows a server cluster/hardware load balancer configuration that does not have an external software load balancer. This is the configuration we are using. Many hardware load balancers provide all of the functionality needed to support https without adding an external software web server.
PPM has a parameter 'ENABLE_WEB_ACCESS_LOGGING'. Please set it to true (com.kintana.core.server.ENABLE_WEB_ACCESS_LOGGING=true) and running kUpdateHtml.sh would turn on request logging in PPM (like a web server's access logs). The logs usually take the form "localhost_access_log.YYYY-MM-DD.txt" and are saved at /server//log . Please set this parameter to true in server.conf and run kUpdateHtml.sh on all nodes. Once that is done, please send us that log so that we can check what is really happening.
The secure logon can not render correct page on logout due to incorrect configuration of server.xsl file by following the Configuring PPM Center with a Load Balancer section on page 15 of PPM 9.10, also check the page 126
we had these kind of issues in one customer and solved with installing certificate to load balacer and changing type to cookie based redirection something like that; you can check with your lb admin there is an option only avaliable after installing certificate.