Hey, guys. I'm still blocked on this earlier part of the discussion: https://lists.wisc.edu/read/archive?id=14421078 Any ideas? (Here's the full thread: https://lists.wisc.edu/read/messages?id=14367795)
-----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Thursday, June 09, 2011 11:05 AM To: [email protected] Subject: Re: [cas-user] Causing CAS to make a REST call at each auth attempt > The API says you MUST never throw an exception unless you want it to stop > the transaction Should read more closely next time ;) > Since its an Audit Trail, the assumption is you let us know you couldn't > determine the user, rather than us trying to discern that from an empty > string, thrown exception, etc. I would argue that it's aborting the transaction in a most undesirable way. We've seen these sorts of Inspektr errors mask the underlying problem in our stack traces, which is really unhelpful. This bring up a point that I feel like we've discussed in the past: "How important is auditing to your application?" For our use of Inspektr in CAS it's just a convenience and we want it to stay out the way. For cases where auditing is a fundamental operation, I can see that audit failure should prevent transactions from committing. I would imagine most CAS deployers feel as we do that it should stay out of the way. Speak up if you feel otherwise. 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 -- 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
