第 5 章 Auditing IdM API operations
Identity Management (IdM) servers use the systemd journal to create audit records of all IdM API operations. To audit operations and troubleshoot issues, you can query the journal to see who performed actions, when, and on which server.
5.1. Overview of IdM API auditing 复制链接链接已复制到粘贴板!
An IdM server records any use of the Identity Management (IdM) API in the systemd journal. This provides a unified method to collect logs for auditing API operations.
The systemd journal allows for centralized collection of logs from individual systems, which can then be queried and filtered.
Each log entry is tagged with an IPA.API marker and contains the following details in a structured format:
-
The authenticated Kerberos principal that performed the action, or
` if the operation was performed by the `rootuser directly on the server through LDAPI. - The name of the API command that was executed.
-
The result of the execution, which is either
SUCCESSor an exception name. - An LDAP backend instance identifier, which is the same for all operations performed as part of the same request.
- A list of arguments and options passed to the command, in JSON format.
You can query these entries with the journalctl utility. Using journalctl with the -x option provides a more detailed, human-readable explanation of the log entry, including links to the relevant documentation.
All IdM API audit entries have a MESSAGE_ID property set to the application UID 6d70f1b493df36478bc3499257cd3b17.