Public sector · Legacy and infrastructure
Omnissa Horizon user provisioning with Okta
Virtual desktop and app delivery platform, formerly VMware Horizon, now sold by Omnissa. SCIM support is not published.
More state government apps →What Okta covers for Omnissa Horizon, 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 Omnissa Horizon account lifecycle.
In the OIN with SWA password fill only. No SAML, OIDC or provisioning.
StitchOps covers 8 of 8 capabilities for Omnissa Horizon.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | Password fill only (SWA). No SAML or OIDC. | Enterprise password management signs users in to Omnissa Horizon with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Omnissa Horizon logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Omnissa Horizon account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Omnissa Horizon roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Omnissa Horizon 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 Omnissa Horizon. | Changes the Omnissa Horizon 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 Omnissa Horizon accounts. | Pulls the Omnissa Horizon user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Omnissa Horizon. | Step level evidence for every action StitchOps takes in Omnissa Horizon. |
Single sign on
Okta, from the OIN
Password fill only (SWA). No SAML or OIDC.
StitchOps
Enterprise password management signs users in to Omnissa Horizon with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Omnissa Horizon 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 Omnissa Horizon 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 Omnissa Horizon 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 Omnissa Horizon 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 Omnissa Horizon.
StitchOps
Changes the Omnissa Horizon 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 Omnissa Horizon accounts.
StitchOps
Pulls the Omnissa Horizon user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Omnissa Horizon.
StitchOps
Step level evidence for every action StitchOps takes in Omnissa Horizon.
Okta coverage from the Okta Integration Network, read October 20, 2026. VMware Horizon View (RADIUS) on okta.com StitchOps for Okta →
SCIM and Okta status
What Omnissa Horizon supports today.
Omnissa Horizon does not publish SCIM support, so we list it as Not published. Ask the vendor before you count on it.
- SCIM status
- Not published
- Okta Integration Network
- In the OIN with SWA password fill only. No SAML, OIDC or provisioning. Read October 20, 2026.
- Vendor
- Omnissa
- Deployment
- On premises
Last verified 2026-10-20.Sources:Product pageOkta Integration Network
More state government apps →Every public sector app →What the SCIM tax is →
What StitchOps automates in Omnissa Horizon.
StitchOps adds and removes users from the directory groups that grant Horizon desktop pools, and pulls the entitlement list for access reviews. The StitchOps worker runs inside your environment, and your data never leaves your network or key vault.
Joiners
Create the Omnissa Horizon account with the right role when your HR system or Okta says someone starts.
Movers and leavers
Change Omnissa Horizon roles when someone changes jobs, and remove access the day they leave.
Password rotation
Rotate shared and service logins in Omnissa Horizon on a schedule and after every offboarding, and update your vault in the same run.
Access review evidence
List who can sign in to Omnissa Horizon on a schedule, compare it to your directory, and keep step level evidence for auditors.
Common questions.
Does Omnissa Horizon support SCIM?
Omnissa Horizon does not publish SCIM support, so we list it as Not published. Ask the vendor before you count on it.
Can Omnissa Horizon accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Omnissa Horizon 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 Omnissa Horizon in the Okta Integration Network?
Yes. As of October 20, 2026, the OIN lists VMware Horizon View (RADIUS) and VMware Horizon View VDI with SWA sign in and no provisioning.
Can Okta deprovision Omnissa Horizon users?
Not through an OIN connector. StitchOps removes Omnissa Horizon accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Omnissa Horizon passwords when someone leaves?
StitchOps logs in to Omnissa Horizon, 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.