We're planning on changing authentication to Peopleadmin to CAS this week. The CAS configuration on both their App and our CAS server has been in place for almost a year now, and was working fine until last week. Peopleadmin swears that they haven't changed a thing, and, I know we haven't changed that CAS server, since the CAS process has been running since 5/19/2014.
HOWEVER, we did apply an update to our F5 load balancer on 6/15, bringing it up to 15.1. From looking through the logfiles on CAS I can see a successful login on 6/12, and, the looping starting on 6/18 (this is a test service, so it doesn't get a lot of access). Has anyone else run into any weirdness like this that's using an F5? I also checked the logs and could see no issues with at least 37 other URL's/services since the update, including external sites like CBORD. I've had them point at our current production CAS server running 3.4.5, as well as out test server running 3.5.2.1 with the same results. Here's the final URL the browser get's from the 3.5.2.1 server: https://castst.wm.edu/cas/login?service=https%3A%2F%2Fwm-sb.peopleadmin.com%2Fhr%2Fsso&renew=1&redirection_loop_intercepted=1 -- 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
