I don't know specifically how to do it (its in our archives though), you can tell mod_proxy to let Tomcat know that its a secure connection.
On Thu, May 31, 2012 at 4:47 PM, Myn Harry <[email protected]> wrote: > Hi: > > We have an evaluation instance of CAS 3.4.11 up and running; the set-up is: > > - SSL URL on load balancer > - Apache on VM, with mod_proxy connections to Tomcat (where CAS is > installed) > > At the moment, the CAS login page is showing message:"You are currently > accessing CAS over a non-secure connection. Single Sign On WILL NOT WORK. > In order to have single sign on work, you MUST log in over HTTPS." > > What is best approach for the message? The connections arriving on Tomcat > will always appear as HTTP as the HTTPS is off-loaded to the load-balancer. > > Thanks. > > > -- > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
