Security posture
Security is anchored in explicit identity boundaries: Okta SAML protects operator access, SCIM bearer tokens protect provisioning ingress, and FreeIPA/LDAP remains the enforcement authority for Linux identity state.
Priority controls
- Validate SAML metadata, ACS routing, certificate fingerprints, group claims, and mapped roles before SSO cutover.
- Scope SCIM tokens to provisioning operations and keep CSRF exemptions narrow, named, and route-specific.
- Redact SAML responses, bearer tokens, bind credentials, secrets, and password material from logs.
- Use TLS, rate limiting, structured audit records, and correlation IDs at every external boundary.
Operational evidence
The platform is strongest when security evidence is visible to operators: SSO event stages, route inventory, health checks, metrics, sync drift, and FreeIPA/Linux validation should all be reviewable without exposing secrets.
- Track SAML login, ACS receipt, signature verification, and session establishment as redacted events.
- Keep OIDC readiness separate from the production SAML path unless it is explicitly enabled.
- Verify FreeIPA connectivity, LDAP result handling, and Linux identity posture through bounded probes.
Next actions
Security depth checklist
- Authenticate transport and authorization at every public ingress.
- Force audit context and secret provenance on all writes.
- Gate critical operations on change window and rollback paths.