Integrations/Connectors
Identity provisioning: SCIM 2.0
What it is
SCIM 2.0 interface for the identity provider (Microsoft Entra ID, Okta) to automatically create, update and deactivate the tenant's accounts and groups. It is people provisioning: it does not generate Findings or Evidence.
How to configure
- In Settings → SSO (as ADMIN), click Generate SCIM token. The token is shown only once: copy it immediately to the IdP's secrets vault. It is revoked in the API key list.
- In the IdP, configure automatic provisioning:
| Field | Entra ID | Okta |
|---|---|---|
| URL | Tenant URL = https://www.etershield.com/api/scim/v2 (the tenant URL is in Settings → SSO) |
SCIM connector base URL = the same |
| Authentication | Secret Token = the SCIM token | HTTP Header with Bearer <token_scim> |
| Identifier | objectId → externalId, userPrincipalName → userName |
Unique identifier field = userName |
| Actions | Users and groups | Push New Users, Push Profile Updates, Push Groups |
- Optional: set the Role per group (group name → role) and the SSO email domains in Settings → SSO.
- Validate the connection ("Test Connection" in Entra) and then with Microsoft's SCIM Validator.
Security rules
- SCIM only accepts a token with the explicit
/api/scim/v2scope. The single tenant API Key and named keys without scopes (full access) are refused (401): creating and deactivating accounts is too much power for a general-purpose key. And the SCIM token, in turn, is not valid on any other route. - Limit of 600 requests/min per tenant (
429if exceeded). - Every operation is recorded in the audit log as
scim:<token name>.
What it does
| In the IdP | In EterShield |
|---|---|
| Assign the user to the application | Creates the account (initial role = the SSO's default JIT role, normally USER); respects the plan's user limit |
| Remove the assignment / deactivate / delete | Deactivates the membership: it never deletes (account and history remain; GDPR anonymization is separate) |
| Reactivate | Reactivates the membership |
Change name, job title (title), externalId |
Updates |
| Group (create, rename, add/remove members) | Creates/updates the tenant department and its member list |
- Role per group: if set, the role of users created by SCIM follows the groups they belong to (precedence ADMIN > MANAGER > USER > AUDITOR > VIEWER). It never assigns
SUPER_ADMINand never leaves the tenant without an administrator. - Last administrator: is never deactivated by SCIM (the IdP receives
400). - Role and status on the membership: role, job title, status and
externalIdlive on the membership (Membership) in this tenant, including the home one; a user created already inactive gets an active account and an inactive membership, and can only sign in to an organization where they have an active membership. - Filters: only
eq:userName/externalIdon Users anddisplayName/externalIdon Groups, which is what Entra and Okta use to find a resource before creating it. Bulk, sorting and ETags are not supported. - External members: if the email sent by the IdP belongs to an account that already exists in another organization (e.g. a consultant from a partner), SCIM does not create a new account: it creates or reactivates that account's membership in this tenant. An external's name and email belong to the home organization and are not changed by this customer's IdP (the request is accepted, those fields are ignored). Deactivating an external removes only their access to this tenant. The tenant can refuse externals in Settings → Security, and an external's entry requires MFA.
- Errors in SCIM format:
400(invalid request/filter, domain outside the SSO),401(token),403(plan limit; externals refused),404,409(duplicateuserName,externalIdor group name),429.
Where it appears in EterShield
People → Access (accounts, with the "External · origin" tag on members from other organizations) and the tenant's departments.