Hi ... if I am understanding you correctly, we do that here (except we use XMLRPC).
We have a cas project using the overlay method (https://wiki.jasig.org/display/CASUM/Best+Practice+-+Setting+Up+CAS+Locally+using+the+Maven2+WAR+Overlay+Method) And I have another maven project that builds jars that the cas overlay project uses when it builds the final war. The jars in my maven project has my code (in my case an XMLRPC call to another service). The overlay contains your changes to configuration files like deployerConfigContext.xml, stuff under view directory, etc. You only need to have those files with changes made by you in the overlay project. So my custom authentication handler that makes the XMLRPC call is configured in deployerConfigContext.xml. Cheers, Andrew ________________________________________ From: Eric Turley [[email protected]] Sent: Tuesday, June 07, 2011 1:12 PM To: [email protected] Subject: [cas-user] Causing CAS to make a REST call at each auth attempt We’d like to make our CAS server make an http call to our “platform” server whenever an auth attempt is made (pass or fail). I’m hoping there’s a way to do that without maintaining a custom version of cas-server-core. I’m looking through the docs to see what I can find, but also sending this email hoping someone can point me in the right direction – either telling me a better way to do it, or telling me the smartest place I should make the call-out happen. Any guidance is appreciated. Thanks ☺ Eric Turley | Sr. Platform Engineer | UTV Ignition Games -- 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 -- 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
