IT · Okta coverage
Iru (formerly Kandji) and Okta: SSO and SCIM
Apple device management and endpoint security, formerly Kandji. SCIM support is not published.
SCIM pricing for every app →What Okta covers for Iru (formerly Kandji), 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 Iru (formerly Kandji) account lifecycle.
In the OIN with SAML or OIDC sign in only. No provisioning.
StitchOps covers 7 of 8 capabilities for Iru (formerly Kandji).
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | SAML or OIDC from the OIN listing. | Needed if your Iru (formerly Kandji) plan doesn't include SSO. Enterprise password management signs users in to Iru (formerly Kandji) with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Iru (formerly Kandji) logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Iru (formerly Kandji) account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Iru (formerly Kandji) roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Iru (formerly Kandji) access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | Users who sign in with SAML or OIDC have no app password. Shared admin logins are not rotated. | Rotates shared admin logins in Iru (formerly Kandji) on a schedule or after an offboarding. |
| Access reviews | No connector to read or remove Iru (formerly Kandji) accounts. | Pulls the Iru (formerly Kandji) user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Iru (formerly Kandji). | Step level evidence for every action StitchOps takes in Iru (formerly Kandji). |
Single sign on
Okta, from the OIN
SAML or OIDC from the OIN listing.
StitchOps
Needed if your Iru (formerly Kandji) plan doesn't include SSO. Enterprise password management signs users in to Iru (formerly Kandji) with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Iru (formerly Kandji) 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 Iru (formerly Kandji) 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 Iru (formerly Kandji) 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 Iru (formerly Kandji) 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
Users who sign in with SAML or OIDC have no app password. Shared admin logins are not rotated.
StitchOps
Rotates shared admin logins in Iru (formerly Kandji) on a schedule or after an offboarding.
Access reviews
Okta, from the OIN
No connector to read or remove Iru (formerly Kandji) accounts.
StitchOps
Pulls the Iru (formerly Kandji) user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Iru (formerly Kandji).
StitchOps
Step level evidence for every action StitchOps takes in Iru (formerly Kandji).
Also in the OIN listing
- Workflows Connectors
Okta coverage from the Okta Integration Network, read October 24, 2026. Kandji on okta.com StitchOps for Okta →
SCIM and API tax
What Iru (formerly Kandji) charges to automate accounts.
Iru (formerly Kandji) does not publish whether SCIM provisioning is included or which plan it needs. Ask the vendor before you count on it, or price it with your own contract in the calculator.
Pricing notes
SAML SSO and Okta SCIM for users and groups are supported; Iru does not publish which plans include them. SCIM needs a custom Okta app because the Okta catalog app does not provision.
Last verified 2026-10-24 (estimate). Source · SCIM pricing for every app · Method
Estimate Iru (formerly Kandji) and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Iru (formerly Kandji) 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 Iru (formerly Kandji) account with the right role when your HR system or identity provider says someone starts.
Movers
Change Iru (formerly Kandji) roles, teams and access when someone changes department or manager.
Leavers
Remove Iru (formerly Kandji) access the same day someone leaves, and free the seat.
Access checks
List who can log in to Iru (formerly Kandji) on a schedule, with evidence for the audit.
Common questions.
Does Iru (formerly Kandji) support SCIM?
Iru (formerly Kandji) does not publish it. Ask the vendor which plan includes SCIM provisioning before you rely on it.
Can Iru (formerly Kandji) accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Iru (formerly Kandji) 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 Iru (formerly Kandji) in the Okta Integration Network?
Yes. As of October 24, 2026, the OIN lists Kandji with SAML sign in and no provisioning. The listing also offers Workflows Connectors.
Can Okta deprovision Iru (formerly Kandji) users?
Not through an OIN connector. StitchOps removes Iru (formerly Kandji) accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
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.