Liferay Audit

  • Enterprise Subscribers Only: Find out how to get a subscription.

Many organizations have the need to produce an audit trail of user actions. In many countries this is mandated by law and the data might need to be stored for a long period time. Liferay's Audit EE app provides a pluggable way of storing the audit trail from Liferay Portal EE and its apps by installing a service. The information is processed by the service in order to store the information into log files, a database, or both. The service leverages Liferay's Lightweight Message Bus and app architecture. The service handles the processing and logging of the audit messages sent through the message bus. Any app can then produce audit messages to the audit message bus destination. A set of audit message producers is implanted as a hook app to provide information on login, logout, user information changes, user role changes, etc. This app specifically registers a new destination (liferay/audit) and listener to the message bus. The listener dispatches the messages to the audit service for processing. Different processors can be registered with the audit service. By default, the app comes with a Database Processor and Log4J Processor. Processors can be either be global or for a specific event type. For instance database processor would be global but Log processor would be only for login events. This app also provides a reporting GUI which allows you to search and browse the audit events stored into database.

This app installs a Liferay service and will appear in your Application menu once installed.

Latest Changes
  • LPS-10988 Custom Model Listener: value.object.listener on plugin portlet sdk project throw java.langClassNotFoundExce...
  • LPS-27993 Update resource actions for audit portlet to remove references to community
  • LPS-30588 Double html escaping in breadcrumbs
  • LPS-30787 6.2.x - IllegalArgumentException and unable to delete a vocabulary that has a category with a subcategory u...
  • LPS-30799 Improve ServiceBeanAutoProxyCreator for backward compatibility
  • LPS-30860 Consolidate "high performance" dynamic query pagination pattern where you query lots of data and performing...
  • LPS-30885 Scheduled Jobs are re-triggered when a node joins the cluster
  • LPS-30936 Add defence from model listener polluting hibernate session 1st level cache
  • LPS-31033 ServiceBuilder is not escaping bad column names when generating SQLQueries
  • LPS-31133 Refine persistence*.ftl
  • LPS-31353 Remove unused persistence references auto injection
  • LPS-31362 Social Networking Friend Request and Accept are not immediately recognized
  • LPS-31997 Simplify DynamicDataSourceTransactionInterceptor creation for plugins
  • LPS-32141 No need to bind blank string query parameter, it can be embeded into SQL string
  • LPS-32185 *PersistenceImpl.find/fetchByPrimaryKey(${entity.PKClassName}) should depend on *PersistenceImpl.find/fetch...
  • LPS-32218 Remove manual boxing from ftl, let the javac do it automatically
  • LPS-33594 PACL - deprecate PACLAdvice
  • LPS-33847 Update Eclipse files to use *-master vs *-trunk nomenclature to fit better with Git vs Svn
  • LPS-34174 Unable to access plugin portlet services from a different plugin portlet (throws UnsupportedOperationExcept...
  • LPS-35118 Modify the PortletDataHandler interface to support preparation of the staged data - like provide content nu...
  • LPS-35131 @Override annotation should be applied to implementations of interface methods
  • LPS-35256 Implement and use a hierarchy stack to avoid storing delete events for child entities
  • LPS-35598 Add deletions to the manifest summary
  • LPS-35647 Replace Control Panel category "Server" with "Apps", reorganizing portlets as necessary
  • LPS-36310 Add "deprecated" attribute to ServiceBuilder entity
  • LPS-36603 DLFolderWrapper and DLFileEntryWrapper do not implement the equals() method for wrapped DLFolder
  • LPS-37529 Audit-portlet Build Failure
  • LPS-37545 Display dates in a more friendly way when listing content
  • LPS-38632 Allow the use of: content/Language*.properties in liferay-hook.xml
  • LPS-39247 Calendar - Errors thrown and portlet error message when adding an event with Add Event button
  • LPS-39961 The Audit Report Portlet's advanced search drop down is not styled correctly
  • LPS-39963 Audit Portlet is missing some language keys
  • LPS-40752 Apply new Search container pattern to Plugins
Show More

Customers Who Viewed This Also Bought