Skip to content

Audit Logs – Track Administrative Actions and Configuration Changes

The Audit Logs page records all significant administrative and security events in MideyeServer. Every configuration change, Assisted Login session, and password reset operation is logged with a timestamp, the identity of the performing user (principal), the event type, and detailed structured data about the operation.

Audit logs are critical for regulatory compliance, security incident investigation, and change management. They provide an immutable trail of who did what, when, and what data was affected — enabling organizations to support requirements in standards such as ISO 27001, SOC 2, and PCI-DSS.

Required Role: ROOT, SUPER_ADMIN, ADMIN, or OPERATOR

Navigation: Home → Logs → Audit Logs

All authenticated users with the required role can view audit logs. This is a read-only view.

The data grid displays audit events with server-side pagination and sorting, defaulting to time descending (newest first) with today’s date range pre-selected.

ColumnHideableDescription
TimeNoTimestamp of the audit event (always visible)
PrincipalNoIdentity of the user who performed the action (always visible)
Event TypeYesCategory of the audit event
Additional InformationYesSummary text describing the action

Click the Filter icon in the toolbar to open the filter panel. All filters are debounced (1-second delay).

FilterTypeDescription
Start DateDate pickerBeginning of the time range (defaults to today at midnight)
End DateDate pickerEnd of the time range (defaults to end of today)
PrincipalText inputFilter by the username of the performing user
Event TypeMulti-selectFilter by one or more event types

Available Event Types:

Event TypeDescription
ASSISTED_LOGINAn assisted login session was initiated, approved, or completed
PASSWORD_RESETA password reset operation was performed through the self-service portal

Click any row to open the detail drawer on the right side. The drawer displays:

  • Time — Event timestamp
  • Principal — User who performed the action
  • Event Type — Category of the event
  • Additional Information — Summary description

Below the summary, the Audit Log Details section renders the event’s structured data as an interactive JSON tree. Key names are translated to human-readable labels where translations are available; otherwise, raw key names are displayed.

The JSON tree is expandable — click on nodes to drill into nested data structures. This enables detailed inspection of exactly what was changed, including before/after values for configuration modifications.

Field NameTypeRequiredDescription
timeZonedDateTimeYesWhen the audit event occurred
principalStringYesIdentity of the user who performed the action
typeAuditEventTypeYesCategory: ASSISTED_LOGIN or PASSWORD_RESET
informationStringNoHuman-readable summary of the action
dataJSONNoStructured detail data (rendered as interactive tree)

Purpose: Narrow down audit events by time range, principal, or event type. Steps:

  1. Click the Filter icon.
  2. Set the desired date range and optional principal or event type filters.
  3. Click Apply.

Result: The data grid updates to show only matching audit events.

Purpose: Reload the latest audit log data. Steps: Click the Refresh (loop) icon in the toolbar. Result: The data grid refreshes with current data.

Purpose: Inspect the full structured data of an audit event. Steps: Click on any row in the data grid. Result: A detail drawer opens on the right with the event summary and an expandable JSON tree of the event data.

  1. Set the date range to cover the audit period (e.g., last quarter).
  2. Review all events to verify that administrative actions are properly logged.
  3. Click on individual events to inspect the detailed data for completeness.
  1. Filter by Principal to find events performed by a specific administrator.
  2. Review the Event Type and Additional Information columns.
  3. Click on the relevant event to view the JSON detail tree showing exactly what was changed.
  1. Filter by Event Type: PASSWORD_RESET.
  2. Review which users performed password resets and when.
  3. Identify any unusual patterns such as high-volume resets from a single principal.
IssuePossible CauseResolution
No audit logs appearDate range too narrowExpand the date range or reset all filters
Principal field shows “system”Automated system actionSome events like scheduled tasks are logged under the system principal
JSON tree shows raw keysMissing translationsUntranslated keys display their raw names; this is expected for lesser-used fields
Expected event not in logsEvent type not currently trackedOnly ASSISTED_LOGIN and PASSWORD_RESET events are captured