-
Title
Does SPS support monitoring SQL Server connections? -
Description
Is it possible to monitor SQL connections using SPS? -
Resolution
RESOLUTION:
- MS SQL connections support was added in SPS version 6.4
Limitations in handling MSSQL connections
- The current version of One Identity Safeguard for Privileged Sessions (SPS) 6.4 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 Desktop Player, 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.
- Only default instance will be used when connection is established and so if multiple instances exist on the same SQL Server then you can establish a connection to other instances by using a different port for each instance.
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.