![]() |
![]() |
e-docs > WebLogic Server > Administration Console Online Help > Security |
Administration Console Online Help
|
Tasks Additional Documentation Attributes
Use this tab to configure an Auditing provider for a security realm. Auditing is the process whereby information about operating requests and the outcome of those requests are collected, stored, and distribued for the purposes of non repudiation. In other words, auditing provides an electronic trail of computer activity. In the WebLogic Server security architecture, an Auditing provider is used to provide auditing services.
If configured, the WebLogic Server Framework will call through to an Auditing provider before and after security operations (such as authentication or authorization) have been performed, enabling audit event recording. The decision to audit a particular event is made by the Auditing provider itself and can be based on specific audit criteria and/or severity levels. The records containing the audit information may be written to output repositories such as an LDAP back-end, database, and a simple file.
By default, the WebLogic Auditing provider is configured. All auditing information is saved in WL_HOME\yourdomain\DefaultAuditRecorder.log.
You can use a Custom Auditing provider instead of the WebLogic Auditing provider. For a Custom Auditing provider to appear on the Auditors tab, the MBean JAR file for the provider must be in the WL_HOME\lib\mbeantypes directory.
Configuring an Auditing Provider
(Requires an Internet connection.)
Introduction to WebLogic Security
Developing Security Providers for WebLogic Server
Securing a WebLogic Server Deployment
Upgrading Security in WebLogic Server Version 6.x to WebLogic Server Version 7.0
The Security page in the WebLogic Server documentation
The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. |
||
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |