NetScaler Going All Secure


When you configure NetScaler Gateway for testing you probably do like me and configure HTTP (80) for everything instead of HTTPS (443) which is a little bit more work.

The main reason why you would and should switch to HTTPS is not because of security, but User Experience. You see, for users to be able to change expired passwords through NetScaler you need to use Secure LDAP (636). Let’s get started!

The first thing you need to do is to setup Active Directory Certificate Services, Create a Domain Certificate and export it. The blog post Securing Citrix X1 StoreFront with Powershell will show you how.

Open Citrix Studio – StoreFront – Server Group – Change Base URL and change from HTTP to HTTPS.

Change Base URL StoreFront

Citrix Studio – StoreFront – Stores – Manage Delivery Controllers – Edit.

Edit Delivery Controller

Connect to StoreFront through SSL and verify that your certificate is valid.

Verify SSL

After testing that SSL works okay it’s time to configure NetScaler.

Citrix Studio – NetScaler Gateway – Secure Ticket Authority – Edit.

Secure Ticket Authority

Check the post Convert .PFX Certificate to PEM Format from Carl Stalhood on how to import and install your Domain Certificate on NetScaler.

Navigate to the NetScaler LDAP policy – edit Server and select SSL from the drop-down list.

Netscaler Change From HTTP to HTTPS 01

A tip from David shows that you can also use SSL.


Change STA from HTTP to HTTPS.

Netscaler Change From HTTP to HTTPS 02

Edit the PL_OS Profile.

Netscaler Change From HTTP to HTTPS 04

Edit the PL_WB Profile.

Netscaler Change From HTTP to HTTPS 06

Netscaler Change From HTTP to HTTPS 07

Save the settings and reboot the NetScaler Gateway.

Set your test users password to expired and log in.

Password Expired

Change Password

And that’s it.


Automation Framework Community Edition

The fastest way to build your lab environment.

Virtual Expo

Friday 30th of September 2022

5 thoughts on “NetScaler Going All Secure”

  1. While the NetScaler supports multiple options, using StartTLS, which is the tip David Pisa posted, is the easier way to secure the traffic. Basically, the LDAP communication starts as plain text over port 389, but a TLS session is negotiated before the data is sent. The advantage is that it is simpler to setup (same port) and most modern OS support it. See RFC2830 for specifics on StartTLS and LDAP.

  2. I agree with the need to go secure, but disagree with your reasoning. Most users don’t have a clue about the differences between http and https, or even care. They generally assume http when they type in a URL, because the browser lets them. This is why I appreciate the NetScaler having responder policies… 😉


Leave a Comment