Operations

Operate the identity path, not just the service process.

FreeSCIM day-two operations center on readiness, synchronization, mappings, reconciliation, drift, audit, federation health, guarded authority changes, and recovery. The goal is to know whether identity intent still matches enforced state.

healthsyncdriftauditrecovery
READY

Path health

Application, database, FreeIPA, federation, and credential readiness are checked independently.

STATE

Sync and drift

Persistent jobs and snapshots show whether source intent and directory state still agree.

PROOF

Audit trail

Actions, outcomes, blockers, and recovery context stay available after the request ends.

Operator surfaces

The first screens should answer “is the identity path healthy?”

Infrastructure controls still matter, but the identity product starts with the systems that determine whether provisioning and enforcement are working.

01

Health and readiness

Service health, database connectivity, directory reachability, secrets readiness, federation state, and guarded feature readiness belong in one operator starting point.

appDBFreeIPAfederation
02

Sync and reconciliation

Persistent sync sessions, job state, change tracking, previews, reconciliations, and summaries make lifecycle movement inspectable before and after apply.

sessionsjobschangesreconcile
03

Mappings

User and group mappings connect source identifiers to FreeIPA objects and give operators a place to diagnose mismatches.

user mapgroup map
04

Drift and snapshots

Read-only drift artifacts and snapshots distinguish expected, cached, and observed state without forcing a write to learn the difference.

snapshotdiffdrift
05

Audit and logs

Application, access, security, sync, federation, and action evidence answer who requested a change, what ran, and what resulted.

auditsecuritysync
06

Authority readiness

Password and federation transitions expose their enablement state, redaction readiness, pilot boundaries, trust health, and rollback posture before scale.

disabledobservepilot
Operator preview

Work the operations command center instead of reading a feature list.

The controls below use the runtime's actual menu vocabulary and operating patterns with sanitized sample state.

Incident workflow

Diagnose the authority chain before changing it.

A useful control plane helps operators narrow the fault domain before reaching for a mutation.

01Check readinessConfirm application, database, source, target, and trust paths.
02Locate identityResolve mapping, active state, profile data, and relevant assignment.
03Compare stateUse sync history, snapshots, and drift before deciding what is wrong.
04Apply bounded actionRun only the mutation owned by the correct authority and current policy.
05Verify and retainObserve downstream state, capture evidence, and keep the rollback path visible.
Supporting operations

Broader system tooling stays available without becoming the product headline.

These surfaces help explain and support the environment around the identity path.

TopologySee relationships among identity, hosts, relays, rooms, storage, and evidence while preserving truth labels. Fleet and classroom contextForeman, Puppet, room inventory, workstation readiness, and bounded power operations. Security observabilityAuthentication, provisioning, remote-session, threat, application, and system evidence with remediation context. Database operationsSchema visibility, backups, retention, migration preview, safe maintenance, and recovery. Federation runtimeApplication readiness, recent failures, claim drift, key freshness, trust state, and rollback readiness. Trust controlsReview the security boundaries that decide what can be enabled, written, exposed, or retained.
Operational memory

Make the second incident cheaper than the first.

Persistent evidence, snapshots, drift, action history, health state, and recovery notes turn troubleshooting into reusable operational knowledge instead of terminal scrollback.

Open runtime truthExplore evidence surfaces