On Sat, Mar 13, 2010 at 10:11 PM, Scott Battaglia <[email protected] > wrote:
> Try out the latest 3.2-RC2-SNAPSHOT from trunk. It should remove the > Spring problems and allow you to test Inspektr. > > Indeed it had. I'm up on 3.4-RC2 and here is a console log (still trying to rewire the Jdbc stuff -- which, as an aside should Inspektr question go somewhere else or is this an appropriate forum?). Audit trail record BEGIN ============================================================= WHO: [username: pberry] WHAT: TGT-2-TzXIZzIqpxB54JF3SBuE9FVEUXJsyg0L3fLRZDMSRRWnhCAIgd-cas-waldorf ACTION: TICKET_GRANTING_TICKET_CREATED APPLICATION: CAS WHEN: Mon Mar 15 09:02:26 PDT 2010 CLIENT IP ADDRESS: 132.241.16.41 SERVER IP ADDRESS: 132.241.16.41 ============================================================= Audit trail record BEGIN ============================================================= WHO: WHAT: TGT-2-TzXIZzIqpxB54JF3SBuE9FVEUXJsyg0L3fLRZDMSRRWnhCAIgd-cas-waldorf ACTION: TICKET_GRANTING_TICKET_DESTROYED APPLICATION: CAS WHEN: Mon Mar 15 09:03:29 PDT 2010 CLIENT IP ADDRESS: 132.241.16.41 SERVER IP ADDRESS: 132.241.16.41 ============================================================= This is from hitting the /login and /logout URLs (not through any application). I'm assuming the logout would still cause a database error due to the not null restriction. File an issue or correct the wiki documentation (I guess that's an issue either way...)? Pat -- 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-dev
