Connectors and connection configuration

This article will outline how to configure settings for the specific connectors.

• Citrix Storefront
• Citrix Netscaler
• Custom Connector
• Microsoft RDS
• Microsoft RDS Multi-Host
• VMware Horizon View
• Desktop Connector

Citrix Storefront

The Citrix Storefront connector supports the following parameters.

• Server URL - This has to be the Store URL (not the StoreWeb URL). You can use the screenshot below as an example;
  • 
• Resource - This will be the resource name your end users see when they log into StoreFront
• Display configuration - This can either be full-screen, or a custom resolution
• Accounts - Lets you choose from previously configured account groups or all accounts
• Launchers - Lets you choose from previously configured launcher groups or all launchers

Citrix Netscaler

The Citrix Netscaler connector only supports nFactor authentication and currently only works with forms-based (traditional username/password logon page) authentication factor such as LDAP. See the following links for configuring nFactor and the requirements [1][2][3].

 

Citrix Netscaler connector options:

• Netscaler URL - This has to be the Netscaler URL.
• Resource - This will be the resource name your end users see when they log into StoreFront
• Display configuration - This can either be full-screen, or a custom resolution
• Accounts - Lets you choose from previously configured account groups or all accounts
• Launchers - Lets you choose from previously configured launcher groups or all launchers

 

 

Custom Connector

This connector can be used when none of the other connector options apply. For example, if your NetScaler version is not supported by our out-of-box connector we do provide the ability to use 3rd party scripts to initiate sessions. The following script can be used to launch a NetScaler session. https://github.com/santiagocardenas/storefront-launcher/

The custom connector supports the following parameters:

• Host - This will be your connection server
• Resource - The resource name your end users see
• Connection command line - this will be the command line we will execute on the launcher machine to initiate a session
• Accounts - Lets you choose from previously configured account groups or all accounts
• Launchers - Lets you choose from previously configured launcher groups or all launchers

Microsoft RDS

The Remote Desktop Session (RDS) connector supports the following parameters.

• RDS Broker / RDS Host - We can connect to an RDS farm or directly to a single desktop
• Resource - When RDS broker has been configured please state the name of the desktop pool here. This value is optional.
• RDS Gateway - Configure the RDS Gateway information if applicable. This value is optional.
• Suppress Certificate Warnings - This allows you to ignore Certificate warnings for untrusted hosts
• Display configuration - This can either be fullscreen, or a custom resolution
• Accounts - Lets you choose from previously configured account groups or all accounts.
• Launchers - Lets you choose from previously configured launcher groups or all launchers.

Microsoft RDS Multi-Host

In versions 4.5.X and onwards you will also be able to specify multiple hosts in a specific farm to connect to. To do so click on the Multi-Hosts config button when creating or modifying an RDS environment.

Next, enter in the details of the RDS servers you wish to have tested.

note: You can also copy and paste a list of machines here for easy entry.

We will always connect to your machines round-robin style. This means that we will connect to machine 1 first, then machine 2, etc.

VMware Horizon View

We use the Horizon View client to launch session as this is the platform that supports launching sessions trough a command line.  This is why we call the view client directly.

We support the following parameters.

• Server URL - This will be your View Server
• Resource - This will be the resource name your end users see
• Connection command line - This contains the path and parameters used by the VMware view executable. The example shown below is the default command line provided by Login Enterprise

• Accounts - Lets you choose from previously configured account groups or all accounts
• Launchers - Lets you choose from previously configured launcher groups or all launchers

You can also add in all accepted parameters for the Horizon View Client. You can refer to the VMware View client documentation for this, VMware View connector reference

Desktop Connector

Login Enterprise has the ability to run on a normal desktop (fat client) just as easily as a virtual desktop. To do this we have created the Desktop Connector. To find out how to use this connection method please click here.