Welcome
Administering
This section describes how to plan for, install, configure, operate, and manage the SafeLinx Server.
Adding and configuring resources
After you complete the installation and initial configuration, continue to prepare the deployment by configuring other network resources.
Securing communications between the SafeLinx Server and other nodes
The SafeLinx Server and the services that it hosts exchange data with clients on the external network and with different types of servers on the internal network. To ensure the privacy of these communications, you can use TLS protocols to encrypt connections between the SafeLinx Server and other nodes.
Managing certificates for SafeLinx
To secure connections between nodes in an HCL SafeLinx deployment over the Transport Layer Security (TLS) protocol requires X.509 certificates stored in a PKCS12 keystore file.
Creating a self-signed certificate
In certain contexts, obtaining a certificate from a third-party certificate authority (CA) is unnecessary. In these cases, you can create a self-signed certificate.

Welcome
Welcome to the HCL SafeLinx documentation, where you can find information about how to install, maintain, and use HCL SafeLinx.
What's new in SafeLinx 1.4?
HCL SafeLinx 1.4 introduces the following new functionality.
Getting started
This information provides an overview for network administrators planning to install HCL SafeLinx. It contains the minimum information that is needed to get you started. For detailed information about installing HCL SafeLinx, see the installation information in the section adminguide/admin_guide.html.
Administering
This section describes how to plan for, install, configure, operate, and manage the SafeLinx Server.
- Overview
  HCL SafeLinx uses standards-based protocols to enable secure access from mobile computing devices outside the firewall to business applications and data on your organization's internal network.
- Security
  HCL SafeLinx includes a range of options for configuring the security of your network, applications, and data.
- Installation planning
  Before you install HCL SafeLinx, verify that you meet the hardware and software requirements, and that the network connections that you want to use are available.
- Roadmaps: Installing and setting up SafeLinx
  The following "roadmap" topics guide you through installing and initially configuring SafeLinx. Refer to the topic that corresponds to your relational database and server operating system.
- Installing and initial configuration
  Initial configuration and installation of HCL SafeLinx varies based on your operating system and relational database.
- Adding a secure login profile
  By default, the SafeLinx Administrator communicates with the access manager over an unencrypted connection. If you want the connection between the SafeLinx Administrator and the access manager to use transport layer security (TLS) protocols, add a secure login profile to the SafeLinx Administrator.
- Adding and configuring resources
  After you complete the installation and initial configuration, continue to prepare the deployment by configuring other network resources.
  - Types of resources
    Before a deployment can support client connections, you must add components to the SafeLinx Server. You use the SafeLinx Administrator to add and configure components. These components include resources to support HTTP access services, mobile access services, and messaging services, and resources to establish security and facilitate administration.
  - Defining a SafeLinx Server by using the SafeLinx Administrator
    Before you can define a SafeLinx Server, you must configure the access manager. If you connect to a SafeLinx Server and its access manager is not yet configured, a wizard leads you through the access manager configuration first. After that process completes, you can configure the SafeLinx Server.
  - Configuring a directory server
    You can configure the SafeLinx Server to retrieve user profile information from an external LDAP server. The directory server that you configure also provides information about how to contact other directory server services. After you configure a directory server, you can assign it to an LDAP-bind authentication profile to authenticate clients when they log in.
  - Securing communications between the SafeLinx Server and other nodes
    The SafeLinx Server and the services that it hosts exchange data with clients on the external network and with different types of servers on the internal network. To ensure the privacy of these communications, you can use TLS protocols to encrypt connections between the SafeLinx Server and other nodes.
    - Securing communications between the SafeLinx Administrator and the access manager
      By default, the SafeLinx Administrator communicates with the access manager over an unencrypted connection. If you run SafeLinx Administrator from a computer that is remote to the SafeLinx Server, you can use TLS protocols to encrypt communications between the two nodes. Use a third-party tool such as OpenSSL to manage the X.509 certificates that are required to establish a secure SafeLinx Administrator session.
    - Securing communications among SafeLinx Servers in a cluster
      For SafeLinx Servers that participate in a cluster, you can use TLS protocols to secure communications between subordinate and principal nodes.
    - Securing communications with an LDAP server
      You can configure Transport Layer Security (TLS) to encrypt communications between the SafeLinx Server and an LDAP server.
    - Securing connections for HTTP access services
      You can configure Transport Layer Security (TLS) to encrypt communications between HTTP access services and other nodes.
    - Configuring secure connections between mobile access services and SafeLinx Clients
      You can use transport layer security (TLS) to encrypt connections between SafeLinx Clients and a mobile access service. To support secure connections from SafeLinx Clients, you install an X.509 certificate on the SafeLinx Server and then configure an HTTPS mobile network connection (MNC) to use that certificate. You can also specify whether the service uses standard TLS ciphers to encrypt the connection or if it must use ciphers that are FIPS 140-2 approved.
    - Managing certificates for SafeLinx
      To secure connections between nodes in an HCL SafeLinx deployment over the Transport Layer Security (TLS) protocol requires X.509 certificates stored in a PKCS12 keystore file.
      - Generating a server certificate from a certificate authority
        For clients to verify a server's identitiy, the certificate authority (CA) must issue a signed server certificate to the server.
      - Creating a PKCS12 keystore file that contains only root certificate chains
      - Creating a self-signed certificate
        In certain contexts, obtaining a certificate from a third-party certificate authority (CA) is unnecessary. In these cases, you can create a self-signed certificate.
      - Installing the root certificate for a third-party certificate authority
        Instead of setting up its own certificate authority (CA), a company may use a third-party certificate authority to sign its server certificates. The client and server must have access to the third-party CA's root certificate to verify the server certificates that are signed by the third-party CA.
      - Requesting a certificate without a signing request
        Some Certificate Authorities do not accept signing request files. Instead, they generate the signing request internally on behalf of the requesting server and then sign it as one transaction. The CA then returns to the server two files, one containing the private key for the server to use and one containing the signed server certificate. In this example, the assumption of the two files is as follows:
  - Adding HTTP access services
    Add one or more HTTP access services to provide secure access to internal applications for remote users who do not have the full HCL SafeLinx VPN client (SafeLinx Client) installed.
  - Configuring an HCL Nomad server
    You can configure a SafeLinx as an HCL Nomad server that acts as a proxy for HCL Nomad clients.
  - Configuring SafeLinx as a reverse proxy for Verse high availability
    You can configure HCL SafeLinx to function as a reverse proxy that distributes requests across HCL Verse servers to provide failover and load balancing.
  - Adding authentication profiles
    Add an authentication profile to specify how HCL SafeLinx authenticates users before it permits access to application servers. SafeLinx supports the following authentication methods: LDAP-bind, RADIUS, and certificate-based.
  - Adding a mobile access service
    If there is no mobile access service configured for the SafeLinx Server, you can add one.
  - Adding messaging services
    Add messaging services to the SafeLinx Server to enable applications to send messages to messaging clients, such as a pager or a phone, over mobile wireless networks. Messaging services include support for short message service (SMS) delivery, and mobile-originated message delivery.
  - Adding users
    If your SafeLinx deployment does not use an external LDAP or RADIUS authentication server, use SafeLinx Administrator to create user accounts. You can add users individually or in a batch mode.
- Administering
  The SafeLinx Administrator administration client is the primary tool for viewing, adding, configuring, and managing HCL SafeLinx resources. Along with the SafeLinx Administrator, you can use the HCL SafeLinx Monitor to view information about packet flow through the SafeLinx Server. You can also use a set of command line tools to perform common SafeLinx Server tasks.
- Programming reference
  There are several programming considerations of which you might want to take advantage.
- Database schema information
  HCL SafeLinx uses a DB2, Oracle, MySQL, or SQL database to store tables of information about current and past activity of SafeLinx Server sessions. The following tables are created and accessed by using the qualifier name wg for DB2 installations.
- Step by step: Nomad configuration
  Here are step-by-step instructions that serve as an example of how to install and configure HCL SafeLinx for Nomad on MySQL on Linux.
SafeLinx Administrator
The SafeLinx Administrator is a Java application that lets administrators configure, monitor, and maintain the resources of one or more SafeLinx Servers.
SafeLinx Clients
SafeLinx Clients can establish virtual private network (VPN) connections with mobile access services across various wireless and wireline network. SafeLinx Clients use these optimized, secure IP tunnels to communicate with resources on the internal network.
Troubleshooting
Use this section to assist you with problems that you might experience, including problems with installation.
Notices

Creating a self-signed certificate

In certain contexts, obtaining a certificate from a third-party certificate authority (CA) is unnecessary. In these cases, you can create a self-signed certificate.

About this task

A self-signed certificate consists of a public/private key pair and a certificate for the public key that is signed by the private key. It is also known as a root certificate because it can be used to create a Certificate Authority.

Self-signed certificates can also be used in simple scenarios when both the client and the server are known to each other and can exchange certificates securely out-of-band.

The following steps describe how to create a self-signed certificate with the OpenSSL toolkit and openssl commands. However, you can use a different key management tool of your choice.

To generate a self-signed certificate:

Procedure

Open the openssl command line to create and initialize a new PKCS12 key store.

Create a new self-signed certificate:

openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes -subj /CN=MyHost.com

Create a PKCS12 file :

openssl pkcs12 -export -in cert.pem -inkey key.pem -out myfile.p12 -name "Alias of cert"