Read a SCIM 2.0 user export
Paste a SCIM ListResponse, an array of User resources or a single User into the checker, or drop the file on the paste box. Every user becomes one line: the user name, whether it is active, its type, its manager, its groups and roles, and when it was created.
What to export
The users of the directory or application, from its SCIM service provider endpoint: GET /Users under the SCIM base URL the provider publishes, with the bearer token it issues. RFC 7644 section 3.4.2 returns a ListResponse with totalResults, startIndex, itemsPerPage and a Resources array; section 3.4.2.4 pages it with startIndex and count. Paste each page one after another; the same user id on two pages is read once.
curl -s -H "Authorization: Bearer $SCIM_TOKEN" \
"https://{scim-base-url}/Users?startIndex=1&count=100"The base URL, the token and the largest page size are set by each service provider; its own SCIM documentation names them.
The fields read
| Field in the export | Read as |
|---|---|
userName | the account (the user name) |
emails (the primary one) | the account, when userName is missing |
displayName, name.formatted | the display name |
userType | the type: Employee, Contractor, a service account or an AI agent, when the provider fills it |
active | enabled: true is enabled, false is disabled and set aside from the findings |
meta.created | created |
meta.lastModified | a note only: when the record last changed |
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User manager (displayName, else value) | the manager, which owns a service, agent or automation account when no owner column exists |
enterprise extension employeeNumber, department | notes |
groups, roles, entitlements (display, else value) | member of: an administrative group or role marks the account privileged |
id | joins pages of the same user; not shown |
What a SCIM export does not carry
- No last login. RFC 7643 defines no last-login or last-used attribute for a User, so every SCIM line reads "last used not recorded" and no dormancy finding can fire from a SCIM export alone.
meta.lastModifiedis when the record changed, not a sign-in, and is never read as one. Some providers add their own extensions; the checker reads none it cannot cite. - No password or credential dates.
passwordis never returned by a SCIM service provider, so last changed is not recorded either. - No owner column. SCIM has a manager in the enterprise extension, not an owner; a service or agent account with no manager comes back as finding 3, no owner named.
- No staff list. Paste one in the second box to check owners against leavers.
The checker reads the JSON in your browser: nothing is uploaded and no connection is made to the system it came from. The JSON is flattened into the same lines a pasted table becomes, so every finding, clause and export works the same. The format name is used to describe the file; the checker is not affiliated with its publisher. Never paste passwords, keys or tokens; the list needs names and dates only.