[Openid-specs-ab] audit in OIDC

Zhanna Tsitkov tsitkova at MIT.EDU
Tue Aug 5 21:20:36 UTC 2014

I am looking at introducing audit feature to OIDC.  More specifically, I would like to have an Audit_id - an identifier that is used for audit purposes and can be traced to the particular participant of the OIDC session.  Audit_id should stay unchanged and be available to all end-to-end participants of the exchange. Once generated, the audit_id can be recorded as part of audit logs at any stage of the exchange and, ideally, be available to downstream RS’s (or somehow deduced/back-traced ).
Audit_id can be either an alpha-numeric string (either randomly generated or something in lines with "audit_id=sub+auth_time+jti") or some json structure.  Audit_id can be generated and signed by OP upon successful end-user authorization and then carried as an optional  parameter in the further processing. Alternatively, as Justin Richer has suggested, one can use access and ID token jti’s as "audit id" and have a table (at the AS) of relationships indexed by token identifier.
The data of interest for audit includes permissions, policies, scopes, claims, authZ, authN related information.  For example, it can be used by government for audit purposes (banks, government agencies), or for audit log dynamic processing for the fast violation response systems, revocations etc.  The relevant Common Criteria document can be found here: http://www.commoncriteriaportal.org/files/ccfiles/CCPART2V3.1R4.pdf

Your input and comments are appreciated.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20140805/a3be6be6/attachment.html>

More information about the Openid-specs-ab mailing list