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.
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 proxy support for HCL Nomad
You can configure a SafeLinx proxy server for HCL Nomad clients.

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.
  - 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.
    - Consolidation of multiple HTTP access services under one IP address
      The HTTP listener now supports configuring multiple HTTP services, each with its own service URL, to use the same IP address and port.
    - Configuring HTTP access: Single URL
      HTTP Access Services provide load balancing and failover for multiple application servers, and different applications over the same service definition (or TCP listen port).
    - URL rewriting for HTTP access services
      By default, when you click a link in a mobile application that connects through HTTP access services, the link opens only if it points to content in the same application. To enable mobile applications such as HCL Connections, iNotes®, and others to render content from links to other internal sites, you can configure the HTTP access service to allow URL rewriting.
    - Adding an application server pool
      Create an application server pool to define a collection of one or more HCL Traveler high-availability clusters. Each cluster can contain multiple Traveler servers. Using an application server pool, you can manage your Traveler clusters as a single entity and balance the load across servers. After you add an application server pool, you assign it to an HTTP access service.
    - Enabling LDAP lookups to determine a user's Traveler server
      HCL SafeLinx manages incoming connection requests from Traveler clients, directing the request to an available Traveler server. With SafeLinx, you can configure the HTTP access service to connect users to a Traveler server specified by an attribute in the user's LDAP record.
    - Specifying path prefixes to identify Traveler requests
      You can configure SafeLinx to recognize one or more path prefixes that are associated with HCL Traveler servers.
    - iNotes® attachment blocking
      To reduce the risk of unauthorized access to confidential information, you can configure SafeLinx to restrict external users from sending or receiving attachments.
    - Client certificate authentication for HTTP access services
      When a client initiates a TLS connection to an HTTP access service, client and server exchange data to negotiate the connection. As part of the negotiation, the HTTP access service always presents a certificate to assure the client that it is connected to the correct server. You can also configure the HTTP access service to require a client browser or application to present a certificate when it initiates the connection. Such mutual authentication protects against man-in-the-middle attacks by providing both participants with proof that they are communicating with the intended party. Client certificates can also be used to authenticate users or devices.
    - Enabling authentication chaining between RADIUS and LDAP for HTTP access services
      With HCL SafeLinx, RADIUS authentication profiles that are used by HTTP access services can be linked to existing LDAP authentication profiles. Enabling this type of authentication chaining allows SafeLinx to verify a user's LDAP credentials before it processes the RADIUS authentication. You can specify the LDAP user ID attribute that you want SafeLinx to use in generating LTPA tokens for single sign-on. RADIUS to LDAP authentication chaining is supported for HTTP access services only.
    - Configuring proxy support for HCL Nomad
      You can configure a SafeLinx proxy server for HCL Nomad clients.
      - Nomad proxy requirements
        Requirements to configure HCL SafeLinx as a proxy for HCL Nomad clients are as follows.
      - Configuring the directory server for Nomad
        Define how SafeLinx communicates with the Domino LDAP service.
      - Creating the authentication profile for Nomad
        Create an LdapBind authentication profile.
      - Adding an HTTP access service for Nomad
        Add an HTTP access service for HCL Nomad.
      - Configuring the Domino LDAP service for Nomad
        Configure the Domino LDAP service to allow searches of required attributes.
      - Adjusting firewall rules for Nomad
        If you deploy SafeLinx in a DMZ as is typical, you may need to modify internal and external firewall rules.
      - Creating a DNS TXT record to streamline connections to the proxy during client setup
        To streamline HCL Nomad users' initial client setup, create a DNS TXT record that directly prompts Nomad users to connect to the SafeLinx server.
      - Nomad security best practices
        Following these security best practices is recommended.
    - Integration with mobile device management (MDM) systems
      With HCL SafeLinx, you can integrate an MDM system with authentication profiles that support HTTP access services. Through the integration, you can enable secondary authentication for mobile devices through an MDM server. The SafeLinx gateway prevents devices that do not comply with MDM policies from connecting to internal resources. SafeLinx currently supports integration with IBM MaaS360.
    - Creating custom login pages
      You can build customized login and logout pages to challenge users to submit their credentials and to display after users end their sessions.
  - 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 proxy support for HCL Nomad

You can configure a SafeLinx proxy server for HCL Nomad clients.

About this task

This functionality provides an authenticating, secure WebSocket server as a front end to Nomad mobile devices, adapts the traffic to Domino NRPC data and relays the data to a HCL Domino® server back-end infrastructure on the Domino native NRPC channel (TCP port 1352).

Complete the following steps:

Procedure

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. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.