Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 5.9.0 - Administration Guide

Preface Introduction The concepts of SPS The Welcome Wizard and the first login Basic settings User management and access control Managing SPS
Controlling SPS: reboot, shutdown Managing Safeguard for Privileged Sessions clusters Managing a high availability SPS cluster Upgrading SPS Managing the SPS license Accessing the SPS console Sealed mode Out-of-band management of SPS Managing the certificates used on SPS
General connection settings HTTP-specific settings ICA-specific settings RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search (classic) interface Using the Search interface Searching session data on a central node in a cluster Advanced authentication and authorization techniques Reports The SPS RPC API The SPS REST API SPS scenarios Troubleshooting SPS Configuring external devices Using SCP with agent-forwarding Security checklist for configuring SPS Jumplists for in-product help Third-party contributions About us

Extracting username from Telnet connections

Purpose:

For specific devices, it is now possible to extract the username from Telnet connections with the help of patterns (including TN3270 and TN5250 systems). Complete the following steps to select the patterns, or request a custom pattern.

Steps:
  1. Navigate to Telnet Control > Authentication Policies and enable Extract username from the traffic.

  2. Click Select target devices to display the list of available target devices. Select the respective device(s) in the Available devices column and click Add.

    NOTE: You can only add one TN3270 specific device to the authentication policy.

    To remove a device from the Target devices column, select it and click Remove.

  3. Click OK. The target devices are listed after Selected devices.

  4. If you cannot find your device in the list of available target devices, request a custom Pattern Set. To do this, contact our Support Team.

  5. To upload the custom pattern set you received, navigate to Telnet Control > Pattern Sets, browse for the file and click Upload.

  6. To delete a custom Pattern Set from SPS, click in the respective row. Generic Pattern Sets cannot be deleted.

Creating and editing protocol-level Telnet settings

Procedure:

Telnet settings determine the parameters of the connection on the protocol level, including timeout value, and so on. Complete the following procedure to create a new Telnet settings profile or edit an existing one:

Caution:

Modifying the Telnet settings is recommended only to advanced users. Do not modify these settings unless you exactly know what you are doing.

Steps:
  1. Navigate to the Settings tab of the Telnet Control menu item and click to create a Telnet setting profile. Enter a name for the profile (for example telnet_special).

  1. Click to display the parameters of the connection.

  2. Modify the parameters as needed. The following parameters are available:

    • Idle timeout: Timeout value for the connection in milliseconds. To avoid early timeout, set it to a larger value, for example a week (604800000 milliseconds).

      Caution:

      Determining if a connection is idle is based on the network traffic generated by the connection, not the activity of the user. For example, if an application or the taskbar of a graphical desktop displays the time which is updated every minute, it generates network traffic every minute, negating the effects of timeout values greater than one minute and preventing SPS from closing the connection.

    • Enable pre channel check: Select this option to evaluate the connection and channel policies before establishing the server-side connection. That way if the connection is not permitted at all, SPS does not establish the server-side connection.

    • Cipher strength: There are various types of cipher strengths defined in OpenSSL. Cipher strength can be set separately for server-side and client-side connections. The following cipher strength settings are available:

      • High: Permit only the use of ciphers that use more than 128-bit long keys. This setting corresponds to the high encryption cipher suites of OpenSSL.

      • Medium: Permit only the use of ciphers that use at least 128-bit long keys. This setting corresponds to the medium encryption cipher suites of OpenSSL.

      • Low: Permit all ciphers. This setting corresponds to the low encryption cipher suites of OpenSSL.

      • Custom: Cipher strength according to openSSL standard. The default setting for custom is to permit every cipher, preferring stronger ciphers.

    • Enable SSLv3: By default, SPS permits only TLS-encrypted connections. Enable this option to permit using the SSLv3 protocol. Note that the SSLv3 protocol is considered to be insecure.

  3. Click Commit.

  1. To display a banner message to the clients before authentication, enter the message into the Banner field. For example, this banner can inform the users that the connection is audited.

  2. Select this settings profile in the TELNET settings field of your connections.

Inband destination selection in Telnet connections

When using inband destination selection in Telnet connections, the user can provide the server address and the username using the following methods:

  • By setting the TELNET ENVIRON option using the SERVER environment variable in the server:port format.

  • By setting the TELNET ENVIRON option using the USER environment variable in the user@server:port format.

  • If neither the SERVER nor the USER environment variable, SPS displays a terminal prompt where the user can enter the username and the server address.

Limitations of using TN5250 protocol with IBM iSeries Access for Windows

Using the TN5250 protocol with IBM iSeries Access for Windows is not supported in non-transparent mode if the client tries to set up all its connections using the IP addresses of SPS (for example, when both the client and SPS are within the same zone and the firewall is behind SPS). This is problematic in the case of an IBM iSeries Access for Windows client, which initiates administrative communication with components other than the Telnet server itself. Bypassing non-audited traffic goes against the purpose of non-transparent mode.

Possible workarounds:

Related Documents