I think Scott is remembering the same the this thread. There are a
couple of ways to introduce ssl flags with apache or even at the
loadbalancer. It's all about adding some ssl info to the http headers:
http://jasig.275507.n4.nabble.com/possible-issue-with-CAS-991-when-offloading-SSL-to-an-LTM-td3728787.html
Regards,
Joachim
On 01.06.2012 03:15, Scott Battaglia wrote:
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]
<mailto:[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 [email protected]
<mailto:[email protected]> as:[email protected]
<mailto:[email protected]>
To unsubscribe, change settings or access archives,
seehttp://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
--
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
