6.Click on same application link. Error. https://trial.acs.utah.edu/uo
fu/fin/Chartfield/?ticket=ST-673-wI4lj4NP6sobUmlGh1pR-cas-test1
That's almost surely some kind of configuration or integration mistake. Any time a ticket parameter is present, it should be in the context of a service parameter that describes the service for which it was issued. The fact that the ticket is expired seems like further support for this hypothesis; the ticket is likely vestigial from a previous access attempt.
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.
A 500 is the expected behavior for an invalid ticket. I'm open to the idea that a 401 or 403 error code is more appropriate -- I know that the behavior of throwing exceptions that are translated by the container to 500 has caused confusion around here.
One of our developers has a designed a work around where he catches the exception
Agreed that's not a pretty fix and likely doesn't address the root problem.
Any thoughts, ideas, are we doing something wrong?
I think you've got a configuration/integration problem particular to PeopleSoft. Beyond that I can't provide any suggestions since I don't have any PS experience. Anyone else?
Best, M -- 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
