SCIM · MANUAL SETUP Production setup tutorial. Trustmi token screens use the real product component with offline teaching data and a deliberately invalid token. Okta screens are reviewed read-only excerpts. Provider-neutral connection cards are examples; field names vary by provider. 00:08 Open your SCIM settings Sign in to Trustmi production and select the organization you want to connect. Open Settings, then Identity and Provisioning, and select SCIM Provisioning. In the earlier settings layout, look under Authentication. You need permission to manage provisioning and tokens. If the page or controls are unavailable, ask your Trustmi administrator or Support to enable the required access. 00:37 Enable SCIM and create a token Turn Enable on and check that the status changes to Enabled. Copy the production endpoint shown on the page: api dot trustmi dot A I, slash scim, slash v two. When there is no active token, select Create Token. If a token is already active, coordinate with its owner before replacing it. A replacement invalidates the previous token and must be coordinated with the connector update. This demonstration uses local teaching data and does not change a real organization. 01:13 Copy the full token now After creating the token, find the highlighted panel that says Copy this token now. Select the copy button beside the full token and save the value in your approved secret store. The full token is shown only once. The Token ID below it is an identifier and cannot authenticate your connector. The value on this screen is deliberately invalid and is only a teaching example. 01:41 Create a SCIM 2.0 connector In your identity platform, open its application or provisioning settings and add a generic SCIM two point zero connector. The exact labels vary by provider. Set the base URL to https colon slash slash api dot trustmi dot A I, slash scim, slash v two. Do not append an organization ID, Users, or Groups to that base URL. If resource paths are requested separately, enter slash Users and slash Groups. The Trustmi token identifies your organization. Keep HTTPS certificate validation enabled. 02:23 Set Bearer authentication Choose Bearer token or API Token authentication. Paste the full Trustmi token into the connector’s protected token field. Do not add Bearer when the field already expects a token. If the connector instead requests a complete HTTP Authorization header, enter Bearer, one space, and the token. Set Accept to application slash scim plus JSON. For JSON request bodies, use the same value for Content Type. No OAuth token exchange is required. 03:00 Test the connection first Save the connector settings and run its connection test. Configure authenticated discovery for Service Provider Config, Schemas, and Resource Types. These endpoints require the same Bearer token. Verify reads from Users and Groups. Start pagination at one and request no more than one hundred records per page. A successful connection test confirms credentials and connectivity; continue with the pilot checks before enabling wider synchronization. 03:34 Map and match the pilot account Map userName to the intended Trustmi sign-in email and configure the primary email value. Map first name, last name, title, and, if needed, enterprise department and division. Do not map passwords, manager, roles or permissions. Match existing accounts before creating a new user. Store Trustmi’s returned SCIM id as the account identifier; externalId is not retained. If creating the pilot returns a conflict, resolve matching with Support. Do not delete an existing account to force creation. 04:14 Configure lifecycle updates Configure routine user updates with PATCH. To suspend the pilot, replace active with false. To reactivate it, replace active with true on the same Trustmi user ID. Verify each result in Trustmi. PATCH supports adding or replacing active, names, title, department and division. It does not support removing attributes or changing username or email. Keep automatic deletion off until its behavior is agreed. User DELETE soft-deletes the account and hides it from SCIM discovery. User PUT is a replacement operation and requires a complete supported profile. 04:59 Configure OU membership If organizational-unit management is required, configure the connector’s Groups resource. A SCIM Group represents a Trustmi organizational unit. Create or match the agreed pilot Group and save its returned ID. Provision the users first. Add membership with a Group PATCH operation using each member’s returned Trustmi User ID. Verify an addition and a removal in Trustmi. Group PUT is unsupported. Department and division are profile values and do not establish membership. Agree Group deletion before enabling it because it deactivates the organizational unit. 05:43 Validate the complete pilot Complete the pilot before expanding synchronization: check account matching or creation, a supported profile update, membership additions and removals, and deactivation and reactivation of the same account. Have a Trustmi administrator confirm roles, permissions and effective organizational-unit access. A generic SCIM connector still needs this validation; connection success alone is not full compatibility. For help, send the provider and connector version, timestamp, request method and path, status and sanitized error. Never include tokens, passwords or Authorization headers.