I am in the same boat as Aruhi. In my previous testing environment, I used CAS 3.3, and we had a similar version for throttling login attempts. It was plugged into loginCongroller, and it was working fine. However, when I tried to plug that interceptor to cas-servlet.xml for cas-server-3.4.2, I could not get it working.
Trying the new configuration (throttleInterceptor) for CAS Server3.4.2 is not working either. From the thread I've read, it seems there was a bug, and it was fixed. I am wondering when the new fix will come out. I am also wondering whether someone has a work around. CAS 3.4.2 uses Spring Web Flow 2, and loginController is no longer used. I am not entirely sure how to plug in some interceptors right after the CAS login process. It would be greatly appreciated if someone could shed some light on this. Thanks, Xuejin -- View this message in context: http://jasig.275507.n4.nabble.com/Re-Using-InMemoryThrottledSubmissionByIpAddressAndUsernameHandlerInterceptorAdapter-in-cas-server-3-2-tp2243622p2281344.html Sent from the CAS Users mailing list archive at Nabble.com. -- 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
