Living network topology

The entire platform becomes one accountable operational graph.

FreeSCIM combines authority, protocol, physical placement, relay selection, runtime health, remote-console readiness, and linked evidence without pretending configured relationships are live traffic.

identity planeLinux authorityfleet and roomsremote pathsevidence linked
FreeSCIM topology connecting identity providers, FreeIPA, Foreman, storage, relays, rooms, and workstations
Truth model

The map shows what is known—and how it is known.

The strongest topology is honest about evidence quality. FreeSCIM visually separates declared architecture, inferred relationships, current observations, and drill-down evidence.

Configured

Known services, declared protocols, room mappings, relay relationships, and ports.

Inferred

Expected directory, Kerberos, DNS, Puppet, storage, and estate relationships.

Observed

Current probes, console readiness, path blockers, health, and runtime state.

Evidence linked

Rooms, workstations, logs, health, operator actions, and recovery detail.

One visual language

From identity intent to a physical seat.

Operators can follow a path from browser authentication and SCIM provisioning into FreeIPA, across Foreman and Puppet inventory, through a room-aware relay, and finally to a workstation action or remote session.

A

Identity and trustOkta, SAML, OIDC, SCIM, password convergence, and session ownership.

B

Infrastructure authorityFreeIPA, DNS, Kerberos, Foreman, Puppet, storage, and host identity.

C

Operational edgeJump relays, WoL relays, rooms, seats, SSH, VNC, Guacamole, and power control.

FreeSCIM control-plane architecture with identity, Linux, fleet, database, remote operations, and endpoint domains
Topology dimensions

Six questions the graph answers immediately.

The topology is a navigation surface and an operational briefing: it should shorten diagnosis, clarify ownership, and prevent the wrong team from chasing the wrong boundary.

Who owns the action?Authentication, provisioning, Linux identity, inventory, remote support, and evidence authorities.
Which path carries it?HTTPS, SCIM, LDAP, Kerberos, DNS, Puppet, SSH, VNC, NFS, and WoL.
Where is it physically?Buildings, rooms, relays, seats, surrounding infrastructure, and workstation identity.
What is healthy now?Healthy, degraded, offline, blocked, unknown, stale, or conflicting—with reasons.
Can support reach it?Actual jump-vantage reachability, selected relay, console type, and launch blocker.
What proves the state?Linked probes, logs, workstation evidence, session actions, and operator context.
AuthorityWho owns truth
PathHow action travels
PlacementWhere systems live
HealthWhat works now
EvidenceWhy the map says so
From map to action

The topology is where diagnosis becomes direction.

Choose a room, workstation, relay, identity system, or protocol edge; inspect the linked evidence; understand the blocker; then take the bounded action from the correct control plane.

Enter infrastructure controlFollow the evidence stream