Download JAR files tagged by auditing with all dependencies

Modular basis for development of crud applications based on ee 10, jpa 3, jsf and primefaces. Aspects covered: security roles, logout, multi lingualism, auditing, theming, lazy loading into data layer, dynamic and named jpa queries, batch processing, wildcards and syntax in parameter values, see OPERATOR Enum.

reference implementation for the scim v2 protocol

This module is part of the eAudit4j audit library, providing a simple and pluggable solution for auditing in Java. This particular Maven module provides a set of audit processors that persists audit events using JDBC. Depending on the processor implementation, the JDBC connection can be instantiated from a configurable database connection pool, a JNDI name, or a data source. Once persisted, the event is passed on without modification.

The eAudit4j library provides a simple and pluggable solution for auditing in Java. This library uses the concept of "audit streams", with a stream being comprised of one or more "audit processors". An application can configure an unlimited number of audit streams, each with a different configuration. When an application wants to audit an event, it will create and populate an "Event" instance, and then submit the event to the audit stream for processing and persitance. Depending on the audit stream configuration and the processors being used in the audit stream configuration, processing my be synchronous or asynchronous, and utilize different security features.

This module is part of a JAAS library that provides common methods for building JAAS modules. It provides common artifacts such as interfaces for auditing, message queue, and credential validation, as well as default implementations of these interfaces. The provided default implementations are not intended for production, and will have to be adjusted to meet deployment specific requirements.

The Liberty Audit feature is used to report and track auditable events to ensure the integrity of your system. The Liberty Audit feature introduces an infrastructure which serves two purposes: - Confirming the effectiveness and integrity of the existing configuration - Identifying areas where improvement to the configuration may be needed The Liberty Audit feature has the ability to capture the following auditable events: - Basic authentication - Start and stop of the Audit service - Form login - Client certificate login - Servlet runAs delegation - Form logout - Servlet 3.0 login, logout and authenticate APIs The Liberty Audit feature supports the Cloud Auditing Data Federation (CADF) event model. The CADF model describes a data model and associated schema definitions for an audit event. The feature provides a default implementation, the AuditFileHandler, which emits human-readable audit records to a file-based log. Each audit record is emitted in JSON format.