One Identity Safeguard for Privileged Sessions 6.4.0 - Administration Guide

Troubleshooting Citrix-related problems

Accessing Citrix servers using the Remote Desktop Protocol

Accessing Citrix servers using the Remote Desktop Protocol may fail in certain situations, and the connection is terminated with the ERROR: error while decompressing packet error message on the client, or with the Event56, TermDD, The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. message on the server.

To overcome this problem, modify the settings of the network card of the server, and disable the Large Send Offload option.

MSSQL-specific settings

The following sections describe configuration settings available only for the MSSQL protocol. Use the following policies to control who, when, and how can access the MSSQL connection. For a list of supported client applications, see Supported protocols and client applications.

• Channel Policy: The MSSQL protocol has only one channel type with no special configuration options. The available channel policy options are the following: Type, From, Target, Time policy, Four-eyes, Record audit trail, Gateway groups, Remote groups, and Content policy. For details on configuring these options, see Creating and editing channel policies.

• TLS support: To enable TLS-encryption for your MSSQL connections, see Enabling TLS-encryption for MSSQL connections.

• Authentication Policy: Authentication policies describe the authentication methods allowed in a connection. Different methods can be used for the client and server-side connections. For details, see Creating a new MSSQL authentication policy.

• MSSQL settings: MSSQL settings determine the parameters of the connection on the protocol level, including timeout value, and so on. For details, see Creating and editing protocol-level MSSQL settings.

• User lists in Channel Policies: User lists affect MSSQL connections only when they are used together with Gateway Authentication. For details, see Configuring gateway authentication.

• Content Policy: Content policies allow you to inspect the content of the connections for various text patterns, and perform an action if the pattern is found. For example, One Identity Safeguard for Privileged Sessions (SPS) can send an e-mail alert if a specific command is used in a MSSQL terminal session. For details, see Creating a new content policy.

• Authentication and Authorization plugin:

  One Identity Safeguard for Privileged Sessions (SPS) provides a plugin framework to integrate SPS to external systems to authenticate or authorize the user before authenticating on the target server. Such plugins can also be used to request additional information from the users, for example, to perform multi-factor authentication.

  For details, see Integrating external authentication and authorization systems.

  NOTE:Some clients (for example, Microsoft SQL Server Management Studio) establish more than one parallel connections at the same time. One Identity Safeguard for Privileged Sessions (SPS) arranges these into separate connections, and their contents are also arranged into separate audit trails.

  AA and Credstore plugins (for example, Starling 2FA plugin) will be called multiple times and can cause unexpected results. In case of plugins that require One-Time Passwords (OTP), the already accepted OTP might suddenly become invalid.

  Also, if you want to use four-eyes authorization configured for your connections, you will have to perform them for each connection.

Topics:

Setting up MSSQL connections

This section focuses on describing the MSSQL-specific details of connection configuration. For a detailed description on configuring connections, see General connection settings.

Topics:

Limitations in handling MSSQL connections

The current version of One Identity Safeguard for Privileged Sessions (SPS) has the following limitations:

• TDS protocol version 7.3 or later is required.
• Due to the TDS protocol version requirement, Microsoft® SQL Server® 2008, or later, is recommended.
• Server responses are currently not indexed and therefore cannot be searched in Search.
• Downloaded audit trails can be opened with BDP, but can only be exported as PCAP.
• The Require Gateway Authentication on the SPS Web Interface option in MSSQL Control > Connections does not work in case of MSSQL connections.