Engineering · Okta coverage
Kiwi TCMS and Okta: SSO, SCIM and offboarding
Open source test case management system. There is no SCIM on any plan.
SCIM pricing for every app →What Okta covers for Kiwi TCMS, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the Kiwi TCMS account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for Kiwi TCMS.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to Kiwi TCMS with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Kiwi TCMS logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Kiwi TCMS account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Kiwi TCMS roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Kiwi TCMS access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in Kiwi TCMS. | Changes the Kiwi TCMS password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove Kiwi TCMS accounts. | Pulls the Kiwi TCMS user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Kiwi TCMS. | Step level evidence for every action StitchOps takes in Kiwi TCMS. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to Kiwi TCMS with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Kiwi TCMS logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the Kiwi TCMS account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes Kiwi TCMS roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes Kiwi TCMS access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in Kiwi TCMS.
StitchOps
Changes the Kiwi TCMS password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove Kiwi TCMS accounts.
StitchOps
Pulls the Kiwi TCMS user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Kiwi TCMS.
StitchOps
Step level evidence for every action StitchOps takes in Kiwi TCMS.
Okta coverage from the Okta Integration Network, read October 10, 2026. Kiwi TCMS has no OIN listing. StitchOps for Okta →
SCIM and API tax
What Kiwi TCMS charges to automate accounts.
Kiwi TCMS does not offer SCIM provisioning on any plan. There is no SCIM tax to pay, and no plan that lets your identity provider create, change and remove Kiwi TCMS accounts through SCIM.
SSO sits on the same plan as SCIM or above it. If you need SSO anyway, that upgrade is not avoidable, and the calculator counts it that way.
Pricing notes
Flat rate per instance subscriptions. Private Tenant $75 a month and Enterprise $400 a month do not document SCIM; login methods cannot be configured per tenant.
Last verified 2026-06-12. Source · SCIM pricing for every app · Method
Pricing data includes the SCIM Tax Index (Iden), CC BY 4.0, https://scimtax.org/. Modified and extended by StitchOps.
Estimate Kiwi TCMS and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Kiwi TCMS accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the Kiwi TCMS account with the right role when your HR system or identity provider says someone starts.
Movers
Change Kiwi TCMS roles, teams and access when someone changes department or manager.
Leavers
Remove Kiwi TCMS access the same day someone leaves, and free the seat.
Access checks
List who can log in to Kiwi TCMS on a schedule, with evidence for the audit.
Common questions.
Does Kiwi TCMS support SCIM?
No. Kiwi TCMS does not offer SCIM provisioning on any plan, so accounts are created and removed by hand, by file import, or by a tool that works in Kiwi TCMS the way an admin would.
Can Kiwi TCMS accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Kiwi TCMS accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is Kiwi TCMS in the Okta Integration Network?
No. As of October 10, 2026, the OIN has no listing for Kiwi TCMS. Okta can sign users in only through a custom app if Kiwi TCMS supports SAML or OIDC, and has no connector to manage Kiwi TCMS accounts.
Can Okta deprovision Kiwi TCMS users?
Not through an OIN connector. StitchOps removes Kiwi TCMS accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Kiwi TCMS passwords when someone leaves?
StitchOps logs in to Kiwi TCMS, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.