You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Alessio Soldano (JIRA)" <ji...@apache.org> on 2013/07/16 00:40:48 UTC
[jira] [Reopened] (CXF-5010) Add customizable request logging
capability to STS
[ https://issues.apache.org/jira/browse/CXF-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano reopened CXF-5010:
----------------------------------
I'm sorry for not having noticed this earlier, but I think I need to reopen this issue. The applied changes have the side effect of having made the STS core dependent on Spring at runtime, while that was not the case previously. We probably need some solution to make the stuff requiring spring optional, as we do e.g. for jaxws tooling, the bus, etc.
> Add customizable request logging capability to STS
> --------------------------------------------------
>
> Key: CXF-5010
> URL: https://issues.apache.org/jira/browse/CXF-5010
> Project: CXF
> Issue Type: New Feature
> Components: STS
> Reporter: Oliver Wulff
> Assignee: Oliver Wulff
> Fix For: 2.7.6, 3.0.0
>
>
> As discussed in [1] add an customizable logging mechanism in the STS thus you can log every successful or failed request. The log message should be customizable what kind of context information should be logged like:
> - issue/validate/...
> - FAILED/SUCCESS
> - principal
> - appliesto
> - token type
> - exception
> - ...
> The Spring eventing mechanism provides an easy way in adding event handling. The event provides all context information like TokenProviderParameters or TokenValidatorParameters, etc for processing.
> A default implementation is provided which uses the CXF Logging API to log the information to a file (or what is configured).
> If you want to change the logging you can just configure a spring bean which implements the Spring ApplicationListener.
> [1] http://cxf.547215.n5.nabble.com/Audit-log-in-CXF-STS-using-ApplicationEventPublisher-td5727425.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira