We're getting ready to deploy updated versions of CAS and Moodle, and are in the process of testing things out. We happened to notice that, in certain situations, there's a redirect loop between the Moodle server and the CAS server. Here is a typical message from CAS Tomcat's catalina.out:
[WARN] HttpClient - Error Sending message to url endpoint [https://.../login/index.php]. Error is [Server redirected too many times (20)] We've noticed that this happens upon logging out from Moodle (that may be the only/main instance where this happens, we're not sure yet). Now, our test Moodle server is just using a self-signed certificate. We were thinking that perhaps this is a factor in the redirect loop -- on the logout, CAS tries to communicate with Moodle, but can't, because it doesn't trust the certificate, so the result is a redirect loop. Is that possible? Will this then go away when we move things to production, and the Moodle server has a real signed certificate? (Or perhaps we can import our self-signed CA's certificate into the truststore on the CAS server so that it trusts our Moodle self-signed certificate?) Or is there something else going on here? Also, we were using this test Moodle server with our old CAS instance (our production instance), and we weren't seeing these errors/loops. Can that be because the configuration is different on that CAS server (e.g., we're doing the service registry different)? (Or it already trusts our self-signed CA?) Thanks for any assistance on this. Milt Epstein Applications Developer Graduate School of Library and Information Science (GSLIS) University of Illinois at Urbana-Champaign (UIUC) [email protected] -- 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
