[JIRA] Updated: (SSPCPP-349) Parseable audit logs for SP

Scott Cantor (JIRA) noreply at shibboleth.net
Fri Sep 9 03:34:26 BST 2011


     [ https://issues.shibboleth.net/jira/browse/SSPCPP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor updated SSPCPP-349:
--------------------------------

    Remaining Estimate: 2 weeks
     Original Estimate: 2 weeks

Plan is to develop a new logging API for audit events and include support for configurable formatting similar to Apache. Actual log output will remain channeled through log4shib in the supplied implementation, but could be replaced.

Eventually this *might* become something more generalized for use with the trace logging, but that's a 3.0 thing.

The best option is probably to wrap as much internal SP state as possible so it can be exposed to the logging plugin.

> Parseable audit logs for SP
> ---------------------------
>
>                 Key: SSPCPP-349
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-349
>             Project: Shibboleth SP - C++
>          Issue Type: New Feature
>          Components: Logging
>            Reporter: Philip Brusten
>            Assignee: Scott Cantor
>             Fix For: 2.5
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> It would be nice if we had an audit-log similar to the audit log from the IdP.
> The transaction log already provides some useful information, but is not easily parseable and does not contain a useful identifier of the user (e.g. REMOTE_USER variable)
> idp-audit.log format: auditEventTime|requestBinding|requestId|relyingPartyId|messageProfileId|assertingPartyId|responseBinding|responseId|principalName|authNMethod|releasedAttributeId1,releasedAttributeId2,|nameIdentifier|assertion1ID,assertion2ID,|
> I think, the SP audit log should contain at least the following fields delimited by a '|':
> - Authentication Time
> - SessionId
> - REMOTE_USER if any
> - Client IP address
> - Authentication Context Class
> - User-agent
> - Application id
> - entityID of SP
> - entityID of IdP
> - Protocol
> - Binding
> - filtered attribute IDs
> Could you take this into consideration?
> Regards,
> Philip

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the commits mailing list