Architecture
FreeSCIM sits between identity providers, SCIM clients, directory services, Linux enforcement, audit sinks, and handoff workflows. The architecture docs explain the boundary model and data flow.
Security model
Operator access, SCIM integration tokens, LDAP credentials, secret storage, CSRF/CSP posture, TLS assumptions, and redacted logs should be reviewed before production writes.
Support model
Support should begin with environment, provider, directory, Linux enforcement, request ID, timestamp, and recent configuration changes. Contact paths are separated into briefing, walkthrough, support, and deployment guidance.
Release and project status
The public site distinguishes verified, supported, integration-ready, and planned capabilities. Claims should stay tied to implementation evidence or clearly marked rollout status.
Operational evidence model
| Evidence | Answers |
|---|---|
| SCIM transaction log | What did the client request and how did FreeSCIM respond? |
| Reconciliation diff | What drift exists between source and directory state? |
| Approval and rollout state | Why was the operation allowed or blocked? |
| Rollback candidate | What recovery action is available? |