Engineering · Okta coverage
ConfigCat and Okta: SSO, SCIM and offboarding
Feature flags and remote config. SCIM support is not published.
SCIM pricing for every app →What Okta covers for ConfigCat, 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 ConfigCat account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for ConfigCat.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to ConfigCat with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares ConfigCat logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the ConfigCat account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes ConfigCat roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes ConfigCat 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 ConfigCat. | Changes the ConfigCat 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 ConfigCat accounts. | Pulls the ConfigCat user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside ConfigCat. | Step level evidence for every action StitchOps takes in ConfigCat. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to ConfigCat with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares ConfigCat 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 ConfigCat 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 ConfigCat 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 ConfigCat 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 ConfigCat.
StitchOps
Changes the ConfigCat 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 ConfigCat accounts.
StitchOps
Pulls the ConfigCat user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside ConfigCat.
StitchOps
Step level evidence for every action StitchOps takes in ConfigCat.
Okta coverage from the Okta Integration Network, read October 10, 2026. ConfigCat has no OIN listing. StitchOps for Okta →
SCIM and API tax
What ConfigCat charges to automate accounts.
ConfigCat 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
Added from Okta deal app lists. SCIM availability and pricing not yet verified.
Last verified 2026-10-10 (estimate). SCIM pricing for every app · Method
Estimate ConfigCat and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate ConfigCat 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 ConfigCat account with the right role when your HR system or identity provider says someone starts.
Movers
Change ConfigCat roles, teams and access when someone changes department or manager.
Leavers
Remove ConfigCat access the same day someone leaves, and free the seat.
Access checks
List who can log in to ConfigCat on a schedule, with evidence for the audit.
Common questions.
Does ConfigCat support SCIM?
ConfigCat does not publish it. Ask the vendor which plan includes SCIM provisioning before you rely on it.
Can ConfigCat accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes ConfigCat 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 ConfigCat in the Okta Integration Network?
No. As of October 10, 2026, the OIN has no listing for ConfigCat. Okta can sign users in only through a custom app if ConfigCat supports SAML or OIDC, and has no connector to manage ConfigCat accounts.
Can Okta deprovision ConfigCat users?
Not through an OIN connector. StitchOps removes ConfigCat accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate ConfigCat passwords when someone leaves?
StitchOps logs in to ConfigCat, 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.