Hi
We're about to embark on our first vCD 8.20 deployment, having had several years experience with vCD 5.1/5.5. As with our current vCD 5.5 portal the vCD cells will be fronted by an F5 BigIP that will function as a load balancer and will also perform two factor authentication.
Our network guys spent considerable time trying to get VMRC working through the F5 (no connection to VMRC), ultimately concluding the problem to be the F5 not recognizing the VMRC session as being related to a valid (e.g. logged in to the F5) user session. There appears to be no obvious session cookie or the like that can be used to relate a vCD user session to an attempt to initiate a VMRC, so the VMRC client gets presented with the F5 login page - this has led them to craft an inelegant workaround based on source IP address that they would strongly prefer not to continue with.
There appears to have been significant changes made to the VMRC between 5.5.x and 8.20, with the introduction of websockets and HTML5 however we have been unable to find anything that goes into the HTTPS and VMRC protocol in enough depth to be able to confirm how to proxy vCD 8.20 VMRC and whether our current setup will even continue to work.
Has anyone successfully configured vCD 8.20 with an F5 load balancer who might be able to share their experience? Just to be clear that the F5 isn't just acting as a load balancer/proxy that exposes the vCD portal & VMRC to the internet - it is performing a user authentication before allowing anyone to reach the vCD portal so it needs to be able to relate your vCD browser session to the VMRC session you just initiated when you clicked on a VM from within it.
Thanks!
Jonathan
