This guide applies to the OIDC-enabled Trustmi integration. If your Okta catalog version only supports SCIM, contact support@trustmi.ai for availability of the OIDC update.
Prerequisites
- Administrator access to Okta and your Trustmi organization.
- Okta SSO enabled for your organization by Trustmi Support.
- Your Trustmi Organization ID. Follow “Find your Organization ID” below before adding the integration in Okta.
- An active Trustmi user whose email matches the assigned Okta user's email. Provision users before sign-in.
Supported features
- SP-initiated OIDC sign-in from Trustmi.
- IdP-initiated sign-in from the Okta End-User Dashboard.
- SCIM user and group provisioning, configured separately.
Just-in-Time (JIT) user creation and Universal Logout are not supported by this integration.
Find your Organization ID
- Sign in to Trustmi and confirm the organization selected in the top navigation.
- Open Settings → Authentication → Single Sign-On.
- If the provider selection screen is displayed, select Okta to open Okta Configuration.
- Find Organization ID in the SSO Configuration Parameters section. During setup, this section is to the right of the Okta Domain, Client ID, and Client Secret fields.
- Click the copy icon next to Organization ID and paste the copied ID into Trustmi Organization ID in Okta. Use only the ID, not a URL.
If SSO is already configured, look for SSO Configuration Parameters below the saved integration. If the ID is not visible or you cannot access this page, contact support@trustmi.ai. Do not delete a working connection to retrieve the ID.
Configuration steps
- Sign in to your Okta Admin Console.
- Go to Applications → Applications and click Browse App Catalog.
- Search for Trustmi, select the Trustmi integration from the Okta Integration Network (OIN) catalog, and click Add Integration.
- Choose an application label that your users will recognize and complete the setup prompts. Use the OIDC-enabled catalog integration. If your existing Trustmi application supports only SCIM, contact Trustmi Support before changing it.
- Set Trustmi Organization ID to your organization's ID.
- Open the integration's Sign On settings and locate Client ID and Client secret. Keep the secret confidential.
- In Trustmi, confirm the selected organization and open Settings → Authentication → Single Sign-On. Select Okta.
-
Enter your Okta organization URL in Okta Domain, for example
https://your-org.okta.com. Do not use the-adminhostname or append/oauth2/default. - Paste the integration's Client ID and Client secret into the corresponding Trustmi fields.
- Click Test Connection, then Save Configuration.
- In Okta, assign the intended users to this application. Their email addresses must match their existing Trustmi accounts.
Verify sign-in
From Trustmi: Open Trustmi sign-in in a private browser window, enter your email and continue. Complete Okta authentication, including MFA when requested. Confirm the correct organization and permissions in Trustmi.
From Okta: Open your Okta End-User Dashboard and select the Trustmi application tile. Complete any authentication prompts and confirm the correct organization in Trustmi.
SCIM provisioning
Follow the Trustmi SCIM configuration guide. The SCIM API token and OIDC client secret are separate credentials. Do not interchange them.
Troubleshooting
- Trustmi shows a password instead of redirecting to Okta: Contact Trustmi Support to confirm that Okta SSO sign-in is enabled for the user's organization. Saving provider credentials alone may not enable email-based SSO routing.
-
Redirect URI mismatch: Check the Trustmi Organization ID in Okta. The callback is
https://api.trustmi.ai/auth/realms/trustmi/broker/<organization-id>/endpoint. If a displayed URL differs, contact Support before changing the integration. - User not assigned: Assign the user to this specific Okta application instance.
- User cannot access Trustmi: Confirm that the user is active, belongs to the intended organization and has the required permissions. JIT provisioning is not supported.
- Invalid client credentials: Verify that the Client ID and Client secret belong to the same application instance and that Okta Domain is your organization URL.
-
Okta administrator returns to Admin Console: Open the End-User Dashboard with
https://your-org.okta.com/app/UserHome?fromAdmin=true, then select the Trustmi tile. Keep your organization's MFA policy enabled.
Support
Contact support@trustmi.ai. Include your organization ID and the error message, but never send passwords, client secrets or API tokens.
Comments
0 comments
Please sign in to leave a comment.