In NetScaler Gateway 11.1
In Citrix Gateway
In All products
Product Documentation
In NetScaler Gateway 11.1
In Citrix Gateway
In All products
NetScaler Gateway Service NetScaler Gateway 12.0 NetScaler Gateway 11.1 NetScaler Gateway 11.0 NetScaler Gateway 10.5 NetScaler Gateway 10.1
View PDF

Configuring NetScaler Gateway and App Controller

January 29, 2019
Contributed by:  C

To enable communication from user devices to the secure network, you need to configure settings in NetScaler Gateway and in App Controller. Citrix recommends running the Quick Configuration wizard to configure these settings, which include settings for App Controller and StoreFront.

When you run the wizard, NetScaler Gateway creates the virtual server and policies that are needed for user connections to App Controller. For more information about running the Quick Configuration wizard, see Configuring Settings with the Quick Configuration Wizard. The Quick Configuration wizard configures the following policies automatically:

  • Virtual server. When you configure a virtual server, you enable SmartAccess mode. When you enable SmartAccess mode (the default setting), this setting also enables clientless access. If users connect by using Receiver for Web, you must install a Universal license on NetScaler Gateway. If you do not install the Universal license, users cannot access Windows-based, web, SaaS, or mobile applications from Receiver for Web or Worx Home.
  • Session policies bound to the virtual server. You create session policies in NetScaler Gateway. You can create the following four session policies:
    • Two session policies manage Receiver and Worx Home connections and web browser connections with Receiver for Web. When you configure the session policy for Receiver, and you want to allow users to connect with Worx Home for iOS, you can enable Secure Browse on the Security tab in the session profile
    • Optionally, if you deploy StoreFront, you can configure a third session policy that manages legacy PNA Services connections from Receiver for Android and Receiver for iOS. If you enable a session policy for PNA Services, users cannot use this connection method from Receiver for Windows.
    • A fourth session policy manages connections to applications and virtual desktops by using the NetScaler Gateway Plug-in. You can also configure Account Services that allows email-based discovery of the StoreFront or NetScaler Gateway web address.
  • Authentication policies bound to the virtual server. You can configure LDAP and RADIUS authentication policies in NetScaler Gateway. If you use two-factor authentication, Citrix recommends using LDAP as the primary authentication policy and RADIUS as the secondary policy.
  • Expressions. In each session policy, you configure expressions, or rules, that use the User-Agent header.
  • Custom clientless access policy. You create a custom clientless access policy to control the rewriting of URLs and how cookies are proxied through NetScaler Gateway.
  • Intranet Applications for Android Worx apps. If you enable split tunneling on NetScaler Gateway, when you configure the IP address routes for Android Worx apps, include the IP addresses of App Controller, the Exchange server (if you are using WorxMail), and all of the IP addresses of internal application web sites that users access from WorxWeb. Bind these settings to the virtual server on NetScaler Gateway.

Configuring App Controller Settings

There are two steps for allowing connections to App Controller applications in the secure network through NetScaler Gateway. In App Controller, you:

  • Configure NetScaler Gateway trust settings.
  • Specify the application to accept connections from remote users.

To route user connections through NetScaler Gateway, you provide the following information:

  • Name for the appliance. This can be any name you choose.
  • Fully qualified domain name (FQDN) to which users connect, such as https://NetScalerGatewayFQDN.
  • FQDN for the callback URL that verifies that the request came from NetScaler Gateway. You use the same FQDN to which users connect. App Controller appends the FQDN automatically with the authentication service URL. For example, the URL appears as https://NetScalerGatewayFQDN/CitrixAuthService/AuthService.asmx.

You can select the web applications that require remote user connections through NetScaler Gateway. When you configure an application in App Controller, you select a check box that identifies that the web application is hosted in the internal network. This adds the VPN keyword to the application and allows the connection request through NetScaler Gateway.

Configuring StoreFront Settings

To support all access methods for users, you need to configure the following settings in StoreFront:

  1. Authentication methods, which include the following settings:
    • User name and password
    • Domain pass-through
    • Pass-through from NetScaler Gateway
  2. The Enable legacy support setting.
  3. NetScaler Gateway settings, including:
    • NetScaler Gateway web address
    • Deployment mode
    • NetScaler Gateway mapped or subnet IP address
    • Logon type as Domain
    • Silent authentication by using the URL https://\<NetScalerGatewayFQDN\>/CitrixAuthService/AuthService.asmx, where NetScalerGatewayFQDN is the FQDN that is in the certificate bound to the virtual server.

If you configure two-factor authentication on NetScaler Gateway, when you configure the settings in StoreFront and you configure the Logon type, select Domain and security token.

Configuring NetScaler Gateway and App Controller

January 29, 2019
Contributed by:  C

In this article

Edit this article