Get started
Go from an empty account to a working SAML or OIDC sign-in in your own app, using a sandbox environment and the hosted test identity provider.
OhAuthCat connects your enterprise customers’ identity providers to your application. Your application still owns its users, permissions and sessions; OhAuthCat hands it a verified profile at the end of each sign-in.
Pick your path
Section titled “Pick your path”| You want to | Start here |
|---|---|
| Add SSO to a Node app with the SDK | Quickstart: Node |
| Add SSO to a Python app with the SDK | Quickstart: Python |
| Let the CLI add the routes to an existing project | Quickstart: ohauthcat init |
| Use another language | SDKs, or the API reference, which has curl, Node and Python for every operation |
| Move from WorkOS, Polis, Auth0 or your own SAML | Migrate |
Before your first sign-in
Section titled “Before your first sign-in”- Create an account, a project and its sandbox environment in the dashboard. Concepts explains accounts, projects, environments and organizations.
- Copy your sandbox keys. Keep the secret key (
sk_test_...) on your server; use the publishable key (pk_...) as the SSO client ID. Register your exact callback URI. - Create an organization for your enterprise customer and a SAML or OIDC connection. In a sandbox you can connect it to the hosted test IdP instead of a real one;
ohauthcat initsets this up for you. - Run the connection test, then activate the connection. A test sign-in records a result; it does not give your app an authorization code.
- Add the sign-in and callback routes with
ohauthcat initor one of the quickstarts.
Next steps
Section titled “Next steps”- Sync users and groups with directory sync, and receive changes as verified webhooks.
- Keep your existing authentication next to enterprise SSO: working with existing auth.
- Use the CLI for browser or device sign-in and named profiles, and read dashboard security before enforcing SSO on your own account.