Common Audit is another new feature of the ForgeRock platform.
Common Audit is part of the platform-wide infrastructure: a framework to handle audit events using common audit event handlers that are plugged in to the individual products. The handlers record events, logging them for example into files, relational databases, or syslog. Because handlers are pluggable, new handlers can be added to interoperate with your systems that store and analyze audit data.
Each audit event is identified by a unique transaction ID. The IDs can be communicated across the products and recorded for each local event. The transaction ID is the means to track requests as they traverse the platform.
In the current platform, configuring handlers depends on the product. So there are several places in the docs to read about how to configure Common Audit:
- OpenAM: Configuring Audit Logging
- OpenDJ: Common ForgeRock Logs
- OpenIDM: Using Audit Logs
- OpenIG: Audit Events and Logging
In addition, if you want to get the source code for Common Audit, or are interested in trying out new handlers and developments, you can find it on the ForgeRock Stash server. Right now it is in the forgerock-audit git repository. (To access most code on the ForgeRock Stash server, sign in with your ForgeRock credentials. You can sign up if you have not done so.)
This blog post was first published @ marginnotes2.wordpress.com, included here with permission.