Connectors and Universal Web Connector

A Connector is a code module that initiates remote desktop sessions through a Connection Broker. It runs as part of the Launcher package, creating new user sessions to remote resources as requested by the Appliance. When the Launcher receives a session request, it uses the Connector to establish the session. For some industry-standard systems, predefined methods automatically communicate with their software to start sessions.

Login Enterprise currently supports six Connector types:

1. Citrix Netscaler 12.1 and 13.0

   • Front-end for Citrix ICA remote sessions

   • Requires server URL, resource name, and display configuration

   • Note: Version 12.1 is end-of-life as of 2022

2. Citrix Storefront

   • Front-end for Citrix ICA remote sessions

   • Requires server URL, resource name, and display configuration

3. Microsoft RDS

   • Supports multiple RDS brokers/servers

   • Optional RDS gateway

   • Requires resource name and display configuration

4. VMware Horizon View

   • Utilizes VMware’s PCoIP remote protocol

   • Requires server URL and resource name

   • Allows editing the connection command line for additional options

5. Desktop

   • Does not create outgoing sessions automatically

   • Requires manual initiation via the Login Processor

6. Custom Connector

   • Specify the host and optional resource

   • Requires a connection command line to initiate the session

   • Launchers monitor the process ID for status

   • Assumes successful logins and lacks detailed status information

Universal Web Connector (UWC)

The Universal Web Connector (UWC) is a versatile software package designed for remote-access systems using web interfaces. It is ideal for scenarios where standard connectors, like Citrix Storefront, may face issues such as multi-factor authentication (MFA) interruptions. The UWC manages interactive steps by interfacing with web browsers, ensuring seamless session initiation.

Implemented as a Custom Connector, the UWC requires downloading and installing the package, making necessary modifications in the Program Files directory, and configuring it within Login Enterprise.