5.2 Installing SSL VPN

Installation time: about 10 minutes.

What you need to know to install SSL VPN

  • Username and password of the administrator.

  • IP address of the Administration Console.

5.2.1 Installing ESP-Enabled SSL VPN

When SSL VPN is deployed without an Access Gateway, an Embedded Service Provider (ESP) component is installed along with SSL VPN. This deployment is called an ESP-enabled SSL VPN. This deployment requires the Administration Console and the Identity Server to be installed before you install SSL VPN.

Deployment Scenarios

ESP-enabled SSL VPN supports the following installation scenarios:

Deployment Scenario 1: Installing SSL VPN on a Separate Machine

This deployment scenario consists of a demilitarized zone where the Identity Server and SSL VPN are deployed separately, without the Access Gateway. For installation instructions for this scenario, see Installing ESP-Enabled SSL VPN. In this scenario, SSL VPN is accessible on port 8443. When it is accessed on port 8080, it will be redirected to port 8443.

Figure 5-1 Deployment Scenario 1

Deployment Scenario 2: Installing SSL VPN and the Identity Server on the Same Machine

This deployment scenario consists of a demilitarized zone where the Identity Server and SSL VPN are on a single machine. The Access Gateway is deployed separately. For installation instructions for this scenario, see Installing ESP-Enabled SSL VPN. In this scenario, SSL VPN will be accessible on secure port 3443. When this port is accessed on a non-secure port 3080, it will be redirected to port 3443.

Figure 5-2 Deployment Scenario 2

Deployment Scenario 3: Installing SSL VPN and the Administration Console on the Same Machine

This deployment scenario consists of a demilitarized zone where SSL VPN, and Administration Console are on the same machine and Access Gateway and the Identity servers are deployed separately. For installation instructions for this scenario, see Installing ESP-Enabled SSL VPN. In this scenario, SSL VPN will be accessible on secure port 8443. When this port is accessed on a non-secure port 8080, it will be redirected to port 8443.

Figure 5-3 Deployment Scenario 3

Deployment Scenario 4: Installing SSL VPN, the Administration Console, and the Identity Server on the Same Machine

This deployment scenario consists of a demilitarized zone where the Identity Server, SSL VPN, and Administration Console are on the same machine and Access Gateway is deployed separately. For installation instructions for this scenario, see Installing ESP-Enabled SSL VPN. In this scenario SSL VPN will be accessible on secure port 3443. When this port is accessed on a non-secure port 3080, it will be redirected to port 3443.

Figure 5-4 Deployment Scenario 4

Installing ESP-Enabled SSL VPN

The following installation steps are applicable to all deployment scenarios of ESP-enabled SSL VPN. The individual scenarios are explained in Deployment Scenarios.

  1. Access the install script.

    1. Ensure that you have downloaded the software or that you have the CD available.

      For software download instructions, see the Access Manager 4.0 Hotfix 1 Readme.

    2. Do one of the following:

      • If you are installing from CD or DVD, insert the disc into the drive, then navigate to the device. The location might be /media/cdrom, /media/cdrecorder, or /media/dvdrecorder, depending on your hardware.

      • If you downloaded the tar.gz file, unzip the file by using the following command:

        tar -xzvf <filename>

    3. Change to the novell-access-manager directory.

  2. Run the following command:

    ./install.sh

  3. Specify 4 to install ESP-Enabled SSL VPN, then press Enter.

  4. Review and accept the License Agreement.

    The following warning is displayed:

    An entry of 127.0.0.2 in the /etc/hosts file affects the Access Manager functionality. Do you want to proceed with removing it (y/n)
    
  5. Specify Y to proceed.

  6. (Conditional) If the SSL VPN machine has been configured with multiple IP addresses, select an IP address for SSL VPN.

  7. Specify the IP address, user ID, and password of the primary Administration Console.

  8. Select the IP address used for the NetIQ Access Manager Server Communications Local Listener. You can select an address, specify a new address, or press Enter to accept the default.

  9. Select the IP address used for the SSL VPN listening IP address. You can select an address, specify a new address, or press Enter to accept the default.

  10. If you are installing SSL VPN on the same machine as the Administration Console, you are not prompted for the IP address of the Administration Console. If the Administration Console is on a different machine, provide the IP address when you are prompted for it.

    Wait while SSL VPN is installed on your system and imported into the Administration Console. This takes few minutes.

    The installation ends with the following message: Installation complete.

  11. To verify the installation of SSL VPN, continue with Section 7.3, Verifying the SSL VPN Installation.

  12. Add an entry in /etc/hosts file to map the SSL VPN IP address with the domain name that the client will use to connect.

  13. If the export law permits and you want to install high bandwidth version of SSL VPN, proceed with Section 5.2.3, Installing the Key for High-Bandwidth SSL VPN.

5.2.2 Installing Traditional SSL VPN

Traditional SSL VPN does not have an ESP and must be configured as a protected resource of an Access Gateway. You can install traditional SSL VPN with Access Gateway Appliance, Identity Server, Administration Console, or on a separate machine.

Deployment Scenarios

Traditional SSL VPN supports the following installation scenarios:

Deployment Scenario 1: Access Gateway and SSL VPN on the Same Server

This deployment scenario consists of a demilitarized zone where the Access Gateway and SSL VPN are on the same server and the Identity Server is deployed separately. For installation instructions for this scenario, see Installing SSL VPN with Access Gateway Appliance. In this scenario, SSL VPN is accessible on port 8443. When it is accessed on port 8080, it will be redirected to port 8443.

Figure 5-5 Deployment Scenario 1

Deployment Scenario 2: SSL VPN Server Installed on a Separate Machine

This deployment scenario consists of a demilitarized zone where the Access Gateway, Identity Server, and SSL VPN are deployed separately. For installation instructions, see Installing Traditional SSL VPN. In this scenario, SSL VPN is accessible on secure port 8443. When this port is accessed on a non-secure port 8080, it will be redirected to port 8443.

Figure 5-6 Deployment Scenario 2

Deployment Scenario 3: Identity Server and SSL VPN on the Same Server

This deployment scenario consists of a demilitarized zone where the Identity Server and SSL VPN are on one machine and the Access Gateway is deployed separately. For installation instructions, see Installing SSL VPN on a Separate Server, with Identity Server, or with Administration Console. In this scenario, SSL VPN will be accessible on secure port 3443. When this port is accessed on a non-secure port 3080, it will be redirected to port 3443.

Deployment Scenario 4: Administration Console and SSL VPN on the Same Server

This deployment scenario consists of a demilitarized zone where the Administration Console and SSL VPN are on one machine and the Access Gateway and Identity Server are deployed separately on different machines. For installation instructions, see Installing SSL VPN on a Separate Server, with Identity Server, or with Administration Console. In this scenario SSL VPN will be accessible on secure port 8443. When this port is accessed on a non-secure port 8080, it will be redirected to port 8443.

Figure 5-7 Deployment Scenario 4

Deployment Scenario 5: Administration Console, Identity Server, and SSL VPN on the Same Server

This deployment scenario consists of a demilitarized zone where the Identity Server, Administration Console, and SSL VPN are on one machine and the Access Gateway is deployed separately. For installation instructions, see Installing SSL VPN on a Separate Server, with Identity Server, or with Administration Console.

In this scenario SSL VPN is accessible on secure port 3443. When this port is accessed on a nonā€secure port 3080, it will be redirected to port 3443.

Figure 5-8 Deployment Scenario 5

Installing Traditional SSL VPN

This section describes the installation procedures for different SSL VPN deployments:

Installing SSL VPN with Access Gateway Appliance

When SSL VPN is installed along with Access Gateway Appliance, the Access Gateway installation process installs SSL VPN along with the Access Gateway.

  1. Start the Access Gateway installation.

    For more information about installing the Access Gateway, see Section 4.1.2, Installing the Access Gateway Appliance.

  2. In the Access Administrator Configuration section, select the Install and Enable SSL VPN Server check box to install and configure SSL VPN with the Access Gateway.

  3. Follow the on-screen instructions to continue with the Access Gateway installation.

  4. If the export law permits and you want to install the high bandwidth version of SSL VPN, proceed with Section 5.2.3, Installing the Key for High-Bandwidth SSL VPN.

Installing SSL VPN on a Separate Server, with Identity Server, or with Administration Console

You can use an install script to install traditional SSL VPN on a separate machine, with the Identity Server, with the Administration Console, or with the Identity Server and the Administration Console.

  1. Access the install script.

    1. Ensure that you have downloaded the software or that you have the CD available.

      For software download instructions, see the Access Manager 4.0 Hotfix 1 Readme.

    2. Do one of the following:

      • If you are installing from CD or DVD, insert the disc into the drive, then navigate to the device. The location might be /media/cdrom, /media/cdrecorder, or /media/dvdrecorder, depending on your hardware.

      • If you downloaded the tar.gz file, unpack the file by using the following command:

        tar -xzvf <filename>

    3. Change to the novell-access-manager directory.

  2. At a command prompt, specify the following install script command:

    ./install.sh

    You are prompted to select an installation.

  3. Specify 3 to install traditional SSL VPN, then press Enter.

  4. Review and accept the License Agreement.

  5. (Optional) If SSL VPN is not installed on same machine as the Administration Console, specify the IP address of the Administration Console.

  6. (Optional) This warning is displayed if an entry of 127.0.0.2 is found in the /etc/hosts file.

    Warning: An entry of 127.0.0.2 in the /etc/hosts file affects the Access Manager functionality. Do you want to proceed with removing it (y/n) [y]?                                                                                                            
    

    Specify Y to proceed.

  7. Specify the user ID and password of the Administration Console administrator.

  8. Specify the SSL VPN Listening IP address. You can select an address, specify a new address, or press Enter to accept the default.

    The following warning is displayed:

    WARNING! SSL VPN will be accessible on ports 3080 (HTTP) and 3443 (HTTPs) when it is installed on the same machine as that of Identity Server. 
    
  9. If the SSL VPN machine has been configured with multiple IP addresses, select an IP address for SSL VPN when you are prompted to do so.

    Wait while SSL VPN is installed on your system and imported into the Administration Console, which takes about 2 minutes.

    The installation ends with the following message: Installation complete.

  10. To verify the installation of SSL VPN, continue with Section 7.3, Verifying the SSL VPN Installation.

  11. If the export law permits and you want to install the high bandwidth version of SSL VPN, proceed with Section 5.2.3, Installing the Key for High-Bandwidth SSL VPN

5.2.3 Installing the Key for High-Bandwidth SSL VPN

Customers who are eligible to install high bandwidth SSL VPN can install the key for high bandwidth SSL VPN after they get the export clearance. This key is installed only for one time. There is no need to upgrade the RPM every time the servlet and the server RPMs for SSL VPN are upgraded. With Access Manager 3.1 or later, you install the key for one time and can upgrade to new versions without installing the key again.

You must install high bandwidth SSL VPN if you want to cluster SSL VPNs.

To install RPM:

  1. Log in to the Novell Customer Center and look for the link that allows you to download the RPM containing key for the high bandwidth version.

  2. Download the following high bandwidth RPM:

    novl-sslvpn-hb-key-3.2-0.noarch.rpm

  3. Log in as root.

  4. Run the following command to stop all services:

    /etc/init.d/novell-sslvpn stop OR rcnovell-sslvpn stop

  5. Run the following command to install RPM:

    rpm -ivh novl-sslvpn-hb-key-3.2.0-0.noarch.rpm

  6. Run the following command to restart all SSL VPN services:

    /etc/init.d/novell-sslvpn start or rcnovell-sslvpn start

  7. Run the following command to check the status:

    /etc/init.d/novell-sslvpn status OR rcnovell-sslvpn status