Home
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.
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 HTTP access services and internal application servers
You can use transport layer security (TLS) to secure connections between the HTTP access service and HTTP proxy servers or application servers on the internal network. To make it easier to configure secure connections to internal application servers, you can enable an HTTP access service to accept untrusted certificates from those servers automatically.

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.
- Installing and initial configuration
  Initial configuration and installation of HCL SafeLinx varies based on your operating system.
- 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 the GSKit to manage the X.509 certificates that you need 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 HTTP access services and internal application servers
        You can use transport layer security (TLS) to secure connections between the HTTP access service and HTTP proxy servers or application servers on the internal network. To make it easier to configure secure connections to internal application servers, you can enable an HTTP access service to accept untrusted certificates from those servers automatically.
      - Configuring secure connections between HTTP access services and clients
        You can use transport layer security (TLS) to encrypt connections between remote HTTP clients and an HTTP access service. You can specify whether the service uses standard TLS ciphers to encrypt the connection or if it uses ciphers that are FIPS 140-2 approved. You can also configure the service to require client devices to present X.509 certificates when they connect to the server.
    - 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 HCL SafeLinx
      Use the GSKit to work with X.509 certificates and key database files.
    - Configuring TLS certificates for messaging services
      You can configure public key certificates to enable transport layer security (TLS) between messaging services and messaging applications on the internal network.
    - Configuring TLS certificates for message processing applications
      To configure a secure connection between the messaging services and applications that use the messaging services and push APIs, configure each endpoint.
  - 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.
  - 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, 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.

Configuring secure connections between HTTP access services and internal application servers

You can use transport layer security (TLS) to secure connections between the HTTP access service and HTTP proxy servers or application servers on the internal network. To make it easier to configure secure connections to internal application servers, you can enable an HTTP access service to accept untrusted certificates from those servers automatically.

About this task

Application servers on the internal network that require secure connections must have X.509 certificates in their key databases so that they can negotiate the TLS handshake. Because the risk of identity-spoofing among internal servers is low, it's typical to install self-signed certificates, rather than purchase signed third-party certificates. However, self-signed certificates can result in connection failures, because the HTTP access server does not have a signer certificate to verify that it can trust the self-signed certificate. To ensure that an HTTP access service does not encounter certificate errors when it tries to connect to internal application servers that use untrusted certificates, enable automatic trust. When you enable automatic trust, there is no need to obtain a trusted root signer certificate and add it to the key database on the SafeLinx Server.

Note: The setting to accept untrusted certificates from internal servers applies to application servers only. To enable secure connections to other types of internal servers, such as an LDAP or database server, you must obtain a copy of the server's certificate and store it in a local key database file.

To configure automatic trust of internal application servers, complete the following procedure.

Procedure

From the Resources pane of the SafeLinx Administrator, right-click the HTTP access service that you want to configure, and then click Properties.
From the Server page of the HTTP Access service properties, select Accept untrusted certificates from internal servers, and then click OK.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.