Security model
How OhAuthCat isolates tenants, encrypts data, controls staff access and validates every sign-in.
A short summary of how the service is protected. For what is built and what is planned, see the trust centre.
Tenant isolation
Section titled “Tenant isolation”Every database query is scoped to one environment, and tests try cross-tenant access on every endpoint. A user signs in only with an email domain that their organization has proven it owns, so a misconfigured identity provider at one company can’t sign in people from another.
Encryption
Section titled “Encryption”- All traffic uses TLS.
- Secrets such as OIDC client secrets and signing keys are envelope-encrypted with keys held in AWS KMS. They are never logged and never shown again after creation.
- SCIM tokens are random 256-bit values, shown once and stored only as hashes. We can’t read them back; rotate one if it is lost.
- Disks, object storage and backups are encrypted with KMS.
Staff access
Section titled “Staff access”Staff reach internal tools only through Cloudflare Zero Trust, signing in with passkeys. Internal tools are not reachable from the public internet. Support access is read-only and needs a stated reason. Every staff action on your account is audited with the staff member and the reason.
Kill switch and suspension
Section titled “Kill switch and suspension”You can switch off a connection or a whole environment. A switched-off environment refuses every sign-in and SCIM request as soon as the running service picks up the change, without reading the database. A suspended account is refused the same way. The dashboard, the management API and webhooks stay available, so you can switch the environment back on. Every change is audited.
Outbound requests and logs
Section titled “Outbound requests and logs”- Webhooks are signed, so you can verify that each one came from us.
- Metadata, discovery and webhook URLs are fetched over HTTPS only, never to private or cloud-metadata addresses, and every redirect is checked again.
- Logs never contain tokens, secrets, SAML payloads or full email addresses.
- Debug bundles are redacted and captured only inside a time-boxed capture window that you open.
Rules every sign-in must pass
Section titled “Rules every sign-in must pass”- Authorization codes expire after 60 seconds and work once. Exchanging one always needs your secret API key.
- Redirects go only to URIs on your allow-list, matched exactly.
- SAML responses are size-limited, parsed once, and identity is read only from the signed element. Exactly one assertion is accepted.
- Responses must answer a request we sent, and each request can be used once. Replays are refused.
- If a database, cache or key service is unavailable, sign-ins may fail. A check is never skipped to keep them working.