立即与支持人员聊天
与支持团队交流

One Identity Safeguard for Privileged Sessions 6.5.0 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS) The Welcome Wizard and the first login Basic settings
Supported web browsers and operating systems The structure of the web interface Network settings Configuring date and time System logging, SNMP and e-mail alerts Configuring system monitoring on SPS Data and configuration backups Archiving and cleanup Forwarding data to third-party systems Joining to One Identity Starling
User management and access control Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing Safeguard for Privileged Sessions (SPS) clusters Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster Upgrading One Identity Safeguard for Privileged Sessions (SPS) Managing the One Identity Safeguard for Privileged Sessions (SPS) license Accessing the One Identity Safeguard for Privileged Sessions (SPS) console Sealed mode Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS) Managing the certificates used on One Identity Safeguard for Privileged Sessions (SPS)
General connection settings HTTP-specific settings ICA-specific settings MSSQL-specific settings RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search interface Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) RPC API The One Identity Safeguard for Privileged Sessions (SPS) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS) Using SPS with SPP Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help Configuring SPS to use an LDAP backend Glossary

One Identity Safeguard for Privileged Sessions (SPS) deployment scenarios in a Citrix environment

This section enlists the available One Identity Safeguard for Privileged Sessions (SPS) deployment scenarios in a Citrix environment. The text on the arrows are formatted in (<step number>) <target port> format. The target ports define the protocols used in the communication:

  • 80: Web service, HTTP: the list of available resources fetched in an XML format from the broker (v12 and v11 with Citrix Virtual Apps (formerly known as Citrix XenApp) only). The broker sends all the necessary information, including secure gateway and server addresses to the client.

  • 8080: XML service, HTTP+XML: application discovery, load balancing (v12 and v11 with Citrix Virtual Apps (formerly known as Citrix XenApp) only), used to fetch target to the application/desktop by the client from the broker (used for load balancing, and so on).

  • 443: XML service access or SOCKS/ICA or CGP/ICA wrapped in TLS. The client communicates with the secure gateway on this port for everything.

  • 1080: SOCKS. The client can be configured to access the target server and the broker using a SOCKS proxy.

  • 1494: Plain ICA.

  • 2598: CGP/ICA (reliable mode enabled).

Caution:

Accessing Citrix Virtual Desktops (formerly known as Citrix XenDesktop) is supported only in the following scenarios. Only reliable connections (CGP) are supported.

Client - SPS - Server (Transparent mode)

The SPS is deployed between the client and the server and the clients use predefined connection files or Program Neighbourhood, without a broker or secure gateway. The clients try to connect to their original ICA/CGP server.

Figure 178: Client - SPS - Server (Transparent mode)

Client - SPS - Server (Non-transparent mode)

The SPS is deployed between the client and the server and the clients use predefined connection files or Program Neighbourhood, without a broker or secure gateway. The clients try to connect to SPS, which can distinguish between the potential targets for example by source IP, or by having multiple IP addresses itself.

Figure 179: Client - SPS - Server (Non-transparent mode)

Client - Broker - SPS - Server (Transparent mode)

The clients are using a farm broker which gives them a list of the available applications and servers, but they do not use a secure gateway in the network. The SPS is placed between the clients and the servers in transparent mode, and it catches the connections when the clients try to connect to the server IP addresses they got from the broker.

Figure 180: Client - Broker - SPS - Server (Transparent mode)

Client - Broker - original secure gateway - Secure Ticket Authority (STA) - SPS - Server

In this setup, a secure gateway is used in the network and the SPS is placed between this gateway and the servers in transparent mode. The clients connect to the broker for the list of available applications/servers and then make their further connections through the original secure gateway. That gateway forwards the connections either to the broker or to the CGP/ICA servers, which latter the SPS intercepts and audits/controls.

Figure 181: Client - Broker - original secure gateway - Secure Ticket Authority (STA) - SPS - Server

Client - Broker - SPS as socks proxy - Server

In this setup, the SPS acts as a SOCKS proxy for the client. It can be set either manually or specified by the broker. The client then makes all its connections to the broker or to the server using SPS as a proxy and hence it can audit/control these connections.

Figure 182: Client - Broker - SPS as socks proxy - Server

To configure such a scenario, you must set the ICA Connection Policy as follows:

  • Enter the IP address of SPS into the To field. This must be the public IP address that the clients will target.

  • Select Inband destination selection, and list the IP addresses or networks of target servers in the Targets field. (For details, see Configuring inband destination selection.)

  • Select Act as a SOCKS proxy.

  • Add the IP addresses of your brokers to the Brokers field.

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.

NOTE:

The problem is not related to using One Identity Safeguard for Privileged Sessions (SPS) in your environment.

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.

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:
相关文档