Directory sync
Directory sync gives each directory a SCIM 2.0 server. Users, groups and memberships provisioned by the IdP are delivered to you as normalised events and can be queried through the API.
Each directory exposes a SCIM 2.0 endpoint for an organization’s IdP. OhAuthCat stores users, groups and memberships and emits directory changes through the Events API and signed webhooks.
Start with SCIM concepts, then implement event processing and ordering. Provisioning and SSO have separate setup status. Organizations without SCIM can use a pulled source: a CSV file on SFTP, or Workday, HiBob, Personio and other HR systems.
Deprovisioning must end application access
Section titled “Deprovisioning must end application access”Your application owns the sessions and access grants it creates. On a verified dsync.user.deleted, or an update whose user state becomes inactive, disable the corresponding local identity and revoke its active application sessions. Remove affected access when memberships are removed according to your application’s policy.
OhAuthCat does not revoke sessions inside Auth0, Cognito, Firebase, Supabase, Clerk or your own session store for you. Implement that action through your supported session system. Keep the directory-user-to-local-user mapping scoped to directory and organization; never apply a deletion across tenants because an email happens to match.
Treat reason=out_of_domain as deprovisioning too. Use durable event processing so an outage does not leave a disabled IdP user signed into your app indefinitely.
Read role mapping before consuming the optional directory-user role. Directory and sign-in roles can differ because directory projection cannot use evidence available only during sign-in. Attribute mappings configure directory sources separately from connection sources. A directory’s mapping can fill built-in fields such as job_title or display_name from a SCIM path as well as custom attributes, and the change applies to the next read of its users.