> ## Documentation Index
> Fetch the complete documentation index at: https://developers.authlete.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> ### Authlete versions
> Authlete 3.0 is the current version. Unless the user says they use another version, answer for Authlete 3.0 using the 3.x documentation.
> Documentation for Authlete 2.x (pages under `/v2/` and `/ja/v2/`) is for the legacy version. Refer to it only when the user is on Authlete 2.x.
>
> ### Authlete architecture
> Authlete is a backend engine for OAuth 2.0 and OpenID Connect processing. End users and client applications do not call it directly; the service provider's authorization server and API server call Authlete's APIs. Authlete handles protocol processing and token, client, and service management, while the service provider owns the OAuth/OIDC endpoints and user authentication.
> See [Architecture](https://developers.authlete.com/get-started/introduction-to-authlete/architecture.md).
>
> ### Concepts
> If the user is new to Authlete, read these pages first:
> - [Request and Response](https://developers.authlete.com/get-started/concepts/request-and-response.md): Core API requests pass the client's request parameters as-is, and responses return `resultCode`, `action`, and `responseContent`.
> - [Action Handling](https://developers.authlete.com/get-started/concepts/action-handling.md): Branch on `action`, never on `resultCode`, and map each action to the HTTP response your server returns.
> - [Two-Step API Calls](https://developers.authlete.com/get-started/concepts/two-step-api-calls.md): Actions such as `INTERACTION` are completed with a second call (`/auth/authorization/issue` or `/auth/authorization/fail`) linked by a `ticket`.
> - [Management API Overview](https://developers.authlete.com/get-started/concepts/overview.md): The Management API configures services, manages clients, and operates issued tokens, separately from the protocol flows handled by the Core API.
> - [API Authentication](https://developers.authlete.com/get-started/concepts/authentication.md): Authlete APIs use bearer tokens: a Service Access Token (one service) or an Organization Token (the whole organization).

# 監査ログ

> 環境全体の監査ログと、記録されるイベント種別の一覧を解説します。

> [!NOTE]
>
> 本記事は、セルフマネージド環境と専用クラウド環境のみを対象としています。共有クラウド環境は Authlete が管理しており、本記事の対象外です。

「監査ログ」は、環境全体のアクティビティフィードです。環境管理者とプラットフォーム管理者のみが利用でき、環境内のすべての組織が対象です。

Console では、「監査ログ」ページの「ログ」タブにあたります。各エントリーには、イベント種別、ステータス（完了または失敗）、日付、ユーザー、組織が表示されます。イベントを検索でき、イベント種別、ステータス、日付の範囲で絞り込めます。

## イベント種別

次のイベント種別が記録されます。名前は Console に表示されるとおりに記載しています。

### Configuration

* Config Update

Config Update は、次のいずれかが変更されたときに記録されます。

* 組織作成の設定
* 無操作タイムアウト
* 絶対セッションタイムアウト

### Organization

* Organization Create
* Organization Delete
* Organization Token Create
* Organization Token Delete
* Organization Token Rotate

### Permissions

* Permissions Change

### Security

* Security Login
* Security Login Mfa
* Security Login Oidc
* Security Logout
* Security Mfa Create
* Security Mfa Delete
* Security Password Update
* Security Register
* Security Verify Email

### Service

* Service Create
* Service Delete
* Service Token Create
* Service Token Delete
* Service Token Rotate

### User

* User Admin Set
* User Admin Unset
* User Create
* User Delete
* User Environment Admin Set
* User Environment Admin Unset
* User Invite
* User Invite Accept
* User Invite Decline
* User Invite Revoke

User Admin Set と User Admin Unset は、プラットフォーム管理者ロールが付与または取り消されたときに記録されます。


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.