> The problem is rather with Oracle as it treats an empty string as NULL - try
> "insert into com_audit_trail (aud_user) values ('');"
Wow, just verified that -- learned something today. Oracle is a world
of surprises.
> We extend AbstractJdbcUsernamePasswordAuthenticationHandler and
> RememberMeCredentials and use our own implementation and configuration for
> login action.
It's hard to imagine those changes are causing problems since the
@Auditable annotations are all on CentralAuthenticationServiceImpl.
In any case it's pretty easy to imagine cases where a ticket can't be
found in the registry. For example, the client is replaying a ticket
that has just been purged by the cleaner process. Probably pretty
rare for service tickets, but for TGTs, I imagine it would be a common
occurrence.
I think you could pretty safely remove the NOT NULL constraint on
AUD_USER. Alternatively, you could subclass
TicketOrCredentialBasedAuditablePrincipalResolver and use a string
like "UNKNOWN" when a ticket can't be found. In the latter case you'd
need to update auditTrailContext.xml accordingly.
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
