Hi all, I don't know if this is a CAS problem or a Browser issue (error occurs on all Browsers).
Here is the scenario: 1. Login into our Peoplesoft portal which is CASified. CAS login presented. Success. 2. Click on link to application that is also CASified. Opens in new window (no CAS login presented, as expected). Success. 3. Close application window. (no CAS logout) 4. Close Peoplesoft window. (no CAS logout) (Now Firefox is completely closed, no other windows or tabs) 5. Open Peoplesoft window (no CAS login presented, expected) 6. Click on same application link. Error. https://trial.acs.utah.edu/uofu/fin/Chartfield/?ticket=ST-673-wI4lj4NP6sobUmlGh1pR-cas-test1 For some reason the second time the application is accessed the ticket is appended to the URL and the service ticket is no longer valid resulting in a 500 error. If I manually remove the ticket from the URL I get into the application just fine. One of our developers has a designed a work around where he catches the exception in a deployment descriptor like this: <error-page> <exception-type>org.jasig.cas.client.validation.TicketValidationException</exception-type> <location>/faces/error.xhtml</location> </error-page> The error page strips the ticket from the url and redirects, the sees nothing. But this seems like a real hassle to tell all our Java CAS client users (ie developers) to do this. Plus the retrofit of 100s of applications. Any thoughts, ideas, are we doing something wrong? Thanks, 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
