SCIM recipe
JumpCloud
Connect a JumpCloud custom SCIM application to Niah.
Contract tested July 30, 2026. The covered Niah operations are exercised by the SCIM compatibility suite: discovery, user create/update/suspend/reactivate, filtering, and group membership changes.
1. Add the application
- In the JumpCloud Admin Portal, add a custom SSO application and enable Identity Management (SCIM).
- Set Base URL to
https://api.niah.si/scim/v2. - Use bearer-token authentication with a Niah organization API key that has
scim:readandscim:write. - Use
userNameas the unique user identifier and test the connection.
2. Configure user attributes
| JumpCloud value | SCIM target |
|---|---|
| Work email / username | userName (required) |
| First name | name.givenName |
| Last name | name.familyName |
| Work email | emails[type eq "work"].value |
| Account enabled | active |
3. Assign users
Assign a test user to the application and verify creation in Niah before assigning production user groups. Profile changes and account suspension are synchronized through PUT or PATCH.
User groups
Assign JumpCloud user groups when they should become Niah teams. Map the group name to displayName and membership to members.
Limitations: nested groups are unsupported; members must already be Niah users in the same organization; group membership cannot grant roles, administrator access, or API scopes; deleting a group removes the team but leaves users active.
Deprovisioning
Configure suspension or unassignment to set active=false. Niah deactivates the organization membership and can reactivate it later with active=true. User DELETE is intentionally unsupported.
Previous recipe← Microsoft Entra IDOverviewSCIM →