I am getting desperate, if I can't resolve this issue my whole CAS project could fail. We have 2 products that must be CASified (Kronos and PeopleSoft).
Anyway we have 2 CAS servers (old CAS version 3.2? and new CAS version 3.4.5). I have a simple test application that works against both CAS servers, it prints out the CAS ticket. Then I have PeopleSoft that only works against old CAS, it can print the ticket. When run against new CAS there is no ticket to print, there is no request parameter "ticket". No matter where I run my new CAS server the above results always hold true. I've tried both Tomcat and Glassfish V3 on various physical servers. All certificates are valid. The test app and PeopleSoft are both behind the same proxy. When I monitor the proxy log I see the ticket in the URL for test application. When I run PeopleSoft against either CAS server I never see the ticket in the URL, yet everything works against the old CAS. For the life of me I cannot figure out where the ticket is getting dropped. The new CAS log file looks the same for both the test app and PeopleSoft. Does anyone have any ideas what else I can do to diagnose this problem? Cheers, Bryan -- 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
