# SCIM conformance tester

Open the tester at [ohauthcat.com/scim-tester](https://ohauthcat.com/scim-tester/). Enter your SCIM server's base URL and a bearer token, preferably one for a test directory.

## What it checks

Each check is a request from your browser to your server, judged against RFC 7643 and RFC 7644 and the behavior identity providers such as Okta and Microsoft Entra ID rely on:

- discovery: the service provider configuration, schemas and resource types endpoints;
- listing users, filtering by `userName` and pagination;
- creating a user, reading it by ID, finding it by filter and refusing a duplicate `userName`;
- deactivating with `PATCH` and deleting;
- error responses, the SCIM media type, and refusing requests without a token.

Write checks touch only one test user that the run creates and then deletes. Turn them off for a read-only run.

## Privacy

Your browser talks to your server directly; nothing goes through OhAuthCat, and we never see your URL, token or users. The token stays in the tab's memory: it is never saved, put in the URL or logged, and it is sent only to the server you entered. See the [privacy model](/tools/#privacy-model).

## Blocked by CORS

Most SCIM servers do not allow requests from browsers. If your server refuses the page's origin, run the same checks from your terminal with [`ohauthcat scim test`](/get-started/cli-commands/#ohauthcat-scim-test), which is not subject to CORS and reads the token from `OHAUTHCAT_SCIM_TOKEN` or a hidden prompt. The tester also shows instructions to run the checks with curl.
