About Omnissa Access Connector 22.09
The Omnissa Access connector is an on-premises component of Omnissa Access that integrates with your on-premises infrastructure such as Active Directory, RSA SecurID®, and Omnissa Horizon® to provide directory integration, user authentication, and virtual apps integration.
The connector contains the following enterprise services:
-
Directory Sync service
Syncs users from Active Directory or LDAP directories to the Omnissa Access service.
-
User Auth service
Provides connector-based authentication methods, including Password (cloud deployment), RSA SecurID (cloud deployment), and RADIUS (cloud deployment).
-
Kerberos Auth service
Provides Kerberos authentication for internal users.
-
Virtual App service
Syncs virtual apps from Horizon, Horizon Cloud Service on Microsoft Azure with Single-Pod Broker or Horizon Cloud Service on IBM Cloud, Citrix®, and ThinApp deployments to the Omnissa Access service.
Note: Integration with Horizon Cloud Service on Microsoft Azure with Universal Broker is configured from the Horizon Cloud administration console and does not require the Virtual App service.
The enterprise services can be installed individually on separate Windows servers or together on the same server. When you install the connector, you select which services to install. The services run independently of each other and can be stopped, started, and managed separately.
All the services, except for the Kerberos Auth service, are outbound and do not require an inbound connection.
The Omnissa Access connector is installed on Windows servers only. See Omnissa Access Connector 22.09 Systems Requirements for supported versions.
Related Documentation
- For information about configuring directories using the Directory Sync service, see Directory Integration with Omnissa Access.
- For information about configuring authentication using the User Auth or Kerberos Auth service, see Managing User Authentication Methods in Omnissa Access.
- For information about configuring virtual apps using the Virtual App service, see Setting up Resources in Omnissa Access.
Was this page helpful?