FreeSCIM network topology showing the control plane, identity systems, Foreman, storage, jump and wake relays, rooms, workstations, and protocol paths
A sanitized representation of the living network-topology surface.

Why the topology page matters

The topology page expresses the whole platform in one operational language. It maps the application and identity plane to FreeIPA, Foreman, storage, gateways, dedicated jump relays, WoL relays, classrooms, and individual workstations. Operators can see not only what exists, but which path is responsible for authentication, provisioning, inventory, power, console access, and recovery.

Truthful evidence model

Configured

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

Inferred

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

Observed

Current workstation probes, console readiness, health, path blockers, and runtime status.

Linked evidence

Drill-down to rooms, workstations, health views, logs, and operator actions.

Topology dimensions

DimensionWhat the map communicates
AuthorityWhich system owns browser authentication, provisioning, Linux identity, authorization, inventory, and operational evidence.
TransportHTTPS, SCIM bearer, LDAP/LDAPS, Kerberos, DNS, Puppet/Foreman, SSH, VNC, NFS, and WoL paths.
Physical contextBuildings, rooms, relays, seats, and surrounding infrastructure.
HealthHealthy, degraded, offline, blocked, unknown, stale, and conflicting states with reasons.
Remote supportWhich jump and Guacamole path reaches each workstation and whether a console can be launched.
SafetyConfigured relationships are not misrepresented as live traffic; sensitive or unrelated overlay addresses are excluded.

From map to action

The map is not decorative. It is a navigation and diagnosis surface: 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.