Prior to downloading this Software, you must review the Software Transaction Agreement located here and confirm, by clicking the I agree check box below, that your organization accepts and is bound by the terms and conditions of the Software Transaction Agreement for this Software.
If you purchased the licenses for this Software by executing an order form with Quest or if you have an agreement with Quest that states that all purchases are governed by such agreement, then the terms and conditions of that agreement supersedes and takes precedence over the Software Transaction Agreement.
One Identity Safeguard for Privileged Sessions is part of One Identity's Privileged Access Management portfolio. Addressing large enterprise needs, Safeguard for Privileged Sessions is a privileged session management solution which provides industry-leading access control, as well as session monitoring and recording to prevent privileged account misuse, facilitate compliance, and accelerate forens...
The RemoteApp Launcher enables users to access an application without revealing credentials and passwords. By using the RemoteApp Launcher, you can protect shared credentials and limit an end user’s access to an allowed or required application.
Users can connect using the IP address of the target server but when trying to connect using the target server hostname, RDP Session fails. Logs show the error: Target address is denied by policy; host='SERVERNAME.DOMAIN.COM', port='3389'
When creating an SPS connection policy that is configured with Inband Destination Selection and adding an asterisk "*" character as a value for targets, this does not allow the SRA Administrator to create SRA connections or tiles in the SRA Web UI and having this limitation, prevents the ability to configure SRA initiated workflow with (User-specific server access restrictions) use-case...
Windows ends support for the RDP client in favor of the Windows App in May 2025; any users who use RDP and RDS that utilize One Identity SPS will need this supported
When attempting to add more than 128 users in the SPS Local User Database, the following error occurs. Invalid configuration nnx.validator.SemanticError: Local User Databases 'LocalUserDBName': At most 128 item(s) allowed, but 129 found; paths=['policies.user_databases.7981267715b8fa0511293f.users'], limit=128, length=129, dbfile='/opt/scb/var/db/scb.xml'
When connecting to a server thorough SPS with SFTP (SSH File Transfer Protocol) the session is working correctly for some time, then it suddenly breaks and disconnects from the server.This can happen typically with clients like WinSCP.
Currently, server_name information extracted from TLS client hello is never forwarded from the client side to the server side. This makes certain web servers which need SNI (Server Name Indication) unreachable via SPS