第 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 `root user directly on the server through LDAPI.
  • The name of the API command that was executed.
  • The result of the execution, which is either SUCCESS or 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.

Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat
返回顶部