This content has been marked as final. Show 1 reply
It's possible this is due to the cas url not being set correctly. In SSOConfig.xml you have two places to set this
casUrl - needs to be set to the external address for cas, this link will be included in pages visible to the end user (eg via webserver or loadbalancer).
casInternalUrl - needs to be set to an internal address for cas, Sites/CS will call this directly (should not go through webserver/loadbalancer)
If these are correct, then try to rule out whether the webserver/loadbalancer is an issue
- is it session sticky?
- if you set casUrl / casInternalUrl to point direct to cas can you login/logout direct to CS without the loadbalancer?