Skip to main content

​
Audit Logs User Guide

Audit logs in Authlete provide a detailed record of security-related events and system activities.
They help administrators understand what happened, who performed it, and when and where it occurred.

​
Overview

Authlete audit logs capture operations such as creating or deleting organizations, services, clients, tokens, and other key events.
All actions — whether performed directly by a user or automatically by a system actor (service principal) — are recorded in a single, unified audit trail.

​
User Types

Each audit log entry identifies the user responsible for the action. Audit logs clearly distinguish between user and service principal activities, ensuring visibility into both human and automated operations.

​
Viewing Audit Logs

Audit logs can be viewed in the Authlete Management Console or accessed via the Authlete API.

​
How to View Audit Logs in the Management Console

  1. Log in to the Authlete Management Console
  2. Choose your Organization name.
  3. Navigate to Organization Settings > Audit Logs
Once you reach the logs page, you can view the following information:

​
Log Filtering

Audit logs can be filtered to help you locate specific entries quickly.
  • Event Type Filter: Show only a specific category of events (e.g., Security Login, User Delete, Client Update).
  • Status Filter: Display only completed or failed events.
  • Date Range Filter: View logs within a selected time period.
  • Free-text Search: Find logs containing specific terms or identifiers.
Audit logs filters Audit Logs Filters

​
Understanding Log Entries

When you select an event, the log entry is displayed in JSON format showing key information about the recorded activity. Audit logs entry example Audit Log Entry Example Each audit log entry may include the following fields:

​
User Event Types

User event types describe activities performed directly by human users through the Authlete Console or APIs.

​
Service Principals in Audit Logs

Some audit entries are generated automatically by internal Authlete services or background processes.
These system-level actors are called Service Principals. Service principals represent trusted services that perform operational or maintenance tasks on behalf of Authlete.
Their actions appear in audit logs the same way user actions do, but with:
  • User Type: a Service Principal
  • User Identifier: The assigned ID or alias of the system actor (for example, migration-service@system.authlete.com)
This ensures full visibility of both human and automated activities within a single, consistent audit view.

​
Service Principal Event Types

Service principal event types record automated actions performed by system-level or background processes.
These events reflect non-human activity such as maintenance or data migration tasks performed by trusted Authlete services. These event types appear alongside user events within the same audit log interface.
Each entry lists its User Type as a Service Principal to indicate that the operation was automated.

​
Summary

Authlete audit logs provide a unified record of all activity — whether performed by users or by automated system actors.
By distinguishing between user and service principal events, Authlete ensures complete transparency, accountability, and traceability across the platform.