Is there any workaround for this that I can do? And, in fact, since we’re not currently interested in Inspektr’s auditing, is there a way I can “turn it off” ?
From: Marvin Addison [mailto:[email protected]] Sent: Wednesday, June 08, 2011 7:26 PM To: [email protected] Subject: Re: [cas-user] Causing CAS to make a REST call at each auth attempt java.lang.IllegalArgumentException: resourceOperatedUpon cannot be null at com.github.inspektr.audit.AuditActionContext.assertNotNull(AuditActionContext.java:81) at com.github.inspektr.audit.AuditActionContext.<init>(AuditActionContext.java:64) at com.github.inspektr.audit.AuditTrailManagementAspect.executeAuditCode(AuditTrailManagementAspect.java:148) at com.github.inspektr.audit.AuditTrailManagementAspect.handleAuditTrail(AuditTrailManagementAspect.java:139) This is a known issue and one that I'm quite sure we should fix. The root cause is that in some cases the resolver throws in the catch block and the resource is never assigned when the finally block executes. If a resource is required, then it should be guaranteed to be assigned. 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
