Change Logs
The Change Logs API provides an audit trail of configuration changes and system modifications in your cidaas instance. Each entry records what changed, when it changed, who made the change, and the previous and new values.
Reports Changelog User ActivityWhy use Change Logs
Keep a durable record of system and configuration changes over time.
Meet regulatory requirements for tracking who changed what and when.
Identify when a configuration change may have caused unexpected behaviour.
Inspect previous values so you can restore or compare configurations with confidence.
What is tracked
Change Logs cover modifications across major areas of the platform:
Change log fields
Each change log entry includes:
| Field | Description |
|---|---|
eventType | Type of change event (for example GROUP_USER_ROLE_ADDED, APP_MODIFIED) |
timeStamp | When the change occurred (ISO 8601) |
sub | User identifier who made the change |
objectType | Type of object that was changed (for example users, apps, usergroups) |
objectId | ID of the object that was changed |
changes | JSON array describing what changed (path, from value, to value) |
oldValue | Previous value before the change |
newValue | New value after the change |
type | Change operation (create, update, delete) |
clientId | Client application that triggered the change |
Access permissions
Admin only: Callers must be members of CIDAAS_ADMINS with the ADMIN or SECONDARY_ADMIN role. They can access all change logs, including changes they initiated themselves.
How to query change logs
CIDAAS_ADMINS with an admin role.changes for field-level diffs, or oldValue / newValue for full object state.Use the Change Logs API to retrieve change log data with filtering and pagination.
Example request
{
"eventType": ["GROUP_USER_ROLE_ADDED", "APP_MODIFIED"],
"objectType": ["usergroups", "apps"],
"from": 0,
"size": 20,
"dateFilter": {
"from_date": "2023-03-02T11:33:55.515Z",
"to_date": "2023-04-02T11:33:55.515Z"
},
"descending": true
}
Filtering options
You can filter change logs by:
- Event type: specific change events (for example
GROUP_CREATED,SCOPE_UPDATED) - Object type: type of object changed (for example
usergroups,apps,scopes) - Object ID: a specific object that was changed
- Date range:
from_dateandto_date - Client ID: a specific client application
- User: filter by user
subwho made the change
Understanding change data
The changes field
The changes field contains a JSON array with field-level details:
[
{
"type": "update",
"path": ["name"],
"from": "Old Name",
"to": "New Name"
}
]
Old value vs new value
| Field | Meaning |
|---|---|
oldValue | Complete object state before the change |
newValue | Complete object state after the change |
changes | Specific fields that changed (more granular) |
Use changes when you need a precise diff. Use oldValue / newValue when you need the full before-and-after documents.
Common use cases
Related documentation
Please contact us directly on our support page or reach out to cidaas support at [email protected].