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