# Get started

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

| You want to                                       | Start here                                                                                                   |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Add SSO to a Node app with the SDK                | [Quickstart: Node](/get-started/quickstart-node/)                                                            |
| Add SSO to a Python app with the SDK              | [Quickstart: Python](/get-started/quickstart-python/)                                                        |
| Let the CLI add the routes to an existing project | [Quickstart: ohauthcat init](/get-started/quickstart-init/)                                                  |
| Use another language                              | [SDKs](/sdks/), or the [API reference](/reference/api/), which has curl, Node and Python for every operation |
| Move from WorkOS, Polis, Auth0 or your own SAML   | [Migrate](/migrate/)                                                                                         |

## Before your first sign-in

1. Create an account, a project and its sandbox environment in the dashboard. [Concepts](/get-started/concepts/) explains accounts, projects, environments and organizations.
2. Copy [your sandbox keys](/get-started/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.
3. 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](/get-started/sandbox-and-test-idp/) instead of a real one; `ohauthcat init` sets this up for you.
4. Run the connection test, then activate the connection. A test sign-in records a result; it does not give your app an authorization code.
5. Add the sign-in and callback routes with [`ohauthcat init`](/get-started/quickstart-init/) or one of the quickstarts.

## Next steps

- Sync users and groups with [directory sync](/directory-sync/), and receive changes as [verified webhooks](/events/webhook-verification/).
- Keep your existing authentication next to enterprise SSO: [working with existing auth](/sso/working-with-existing-auth/).
- Use the [CLI](/get-started/cli/) for browser or device sign-in and named profiles, and read [dashboard security](/get-started/dashboard-security/) before enforcing SSO on your own account.
