I think you should leave cas.server.httpProxy.secure=true, this is actually 
setting on container connector the CAS is checking.

Jozef

On Thursday, December 14, 2017 at 5:50:59 AM UTC+1, casuser wrote:
>
> There is a load balancer in between the user and the CAS . The load 
> balancer will check allow the SSL certificate. But from the load balancer 
> to the CAS the connection will be HTTP. 
>
> How to configure cas in that way so that it listen to HTTP?
>
> I have tried this in my cas.properties but didn't solve my problem:
>
>
> cas.server.httpProxy.enabled=true
> cas.server.httpProxy.secure=false ## changed from True
> cas.server.httpProxy.protocol=AJP/1.3
> cas.server.httpProxy.scheme=http ## changed to http
> cas.server.httpProxy.redirectPort=8080
> cas.server.httpProxy.proxyPort=8080
> cas.server.httpProxy.attributes.attributeName=attributeValue
>
> I do have the warning: 
> "Non-secure Connection 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." but the warning still remains. 
> "
> https://apereo.github.io/cas/5.2.x/installation/Configuration-Properties.html#http-proxying";
>  
>
> CAS Properties 
> <https://apereo.github.io/cas/5.2.x/installation/Configuration-Properties.html#http-proxying>
> apereo.github.io
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/d7221bc8-0d63-4e5d-844d-1fb57b7402e8%40apereo.org.

Reply via email to