On Tue, 8 Nov 2016, Harish Reddy wrote:
<https://lh3.googleusercontent.com/-Jn3EbvCFKQY/WCGJPYp5eEI/AAAAAAAAB2Q/63I_6mXk6zc0Fgnt2rDT7Kh52xEkFLhFQCLcB/s1600/Screenshot%2Bfrom%2B2016-11-08%2B13%253A38%253A58.png>
Even though the demo app has a SSL certificate.CAS app still displays this
error
You are currently accessing CAS over a non-secure connection
If Demo app has bugs like this, how can a normal user trust CAS server?
It appears the folks that setup the demo site are proxying the connection
(probably from Apache HTTPD to Tomcat), but Tomcat doesn't know that it is
being accessed over HTTPS. Whoever runs the demo site can look into this.
Harish, that warning/error happens because the CAS server software
refuses to run over an insecure connection, which is a good thing!
Andy
