Chat now with support
Chat with Support

One Identity Safeguard for Privileged Passwords 6.0 LTS - Release Notes

Known issues

The following is a list of issues known to exist at the time of release.

Known issue

Issue ID

Safeguard for Privileged Passwords does not support Powershell v6.0 or greater. Use either the Windows command shell or a Powershell version less than 6.0 as the default shell configured for Open SSH sessions on a Windows asset.


If you have an on-prem VM (Hyper-V or VMware), the following actions may be needed to move to Safeguard for Privileged Passwords v6.0 based on your installation. (These issues do not affect hardware appliances or cloud VMs.)

  • If you upgrade from v2.x to v6.0 then restore a backup taken prior to 6.0, you will need to reassign session connections. See KB article 315569 for resolution steps.
  • After upgrading to v6.0, or after restoring a backup taken prior to 6.0 while running 6.0, the log on to an existing External Federation provider will fail. See KB article 315570 to for the steps to edit the app registration’s Application ID URI.


If you are using the web UI to launch RDP sessions, consider the following which is applicable for versions 2.11 and 2.11.1:

(missing or bad snippet)

Accounts cannot be added through the Toolbox by clicking . Instead, navigate to Administrative Tools | Accounts and click  Add Account from the toolbar.


System requirements

Safeguard for Privileged Passwords has several graphical user interfaces that allow you to manage access requests, approvals, and reviews for your managed accounts and systems:

  • The Windows desktop client consists of an end-user view and administrator view. The fully featured desktop client exposes all of the functionality of Safeguard based on the role of the authenticated user.
  • The web client is functionally similar to the desktop client end-user view and useful for requestors, reviewers, and approvers. Many administration functions are available as well. The web client is sometimes called the Windows client.
  • The web management console displays whenever you connect to the virtual appliance and is used for first time configuration.
    When setting up a virtual environment, carefully consider the configuration aspects such as CPU, memory availability, I/O subsystem, and network infrastructure to ensure the virtual layer has the necessary resources available. See One Identity's Product Support Policies for more information on environment virtualization.

Ensure that your system meets the minimum hardware and software requirements for these clients.

If a Safeguard Sessions Appliance is joined to Safeguard for Privileged Passwords, session recording is handled via Safeguard for Privileged Session. The join is initiated from Safeguard for Privileged Sessions. For details about the join steps and issue resolution, see the One Identity Safeguard for Privileged Sessions Administration Guide.


It is recommended that connection, including overhead, is faster than 10 megabits per second inter-site bandwidth with a one-way latency of less than 500 milliseconds. If you are using traffic shaping, you must allow sufficient bandwidth and priority to port 655 UDP/TCP in the shaping profile. These numbers are offered as a guideline only in that other factors could require additional network tuning. These factors include but are not limited to: jitter, packet loss, response time, usage, and network saturation. If there are any further questions, please check with your Network Administration team.

Desktop client system requirements

The desktop client is a native Windows application suitable for use on end-user machines. You install the desktop client by means of an MSI package that you can download from the appliance web client portal. You do not need administrator privileges to install Safeguard for Privileged Passwords.

NOTE: PuTTY is used to launch the SSH client for SSH session requests and is included in the install. The desktop client looks for any user-installed PuTTY in the following locations:

  • Any reference to putty in the PATH environment variable
  • c:/Program Files/Putty
  • c:/Program Files(x86)/Putty
  • c:/Putty

If PuTTY is not found, the desktop client uses the version of PuTTY that it installed at:


If the user later installs PuTTY in any of the locations above, the desktop client uses that version which ensures the user has the latest version of PuTTY.

Table 2: Desktop client requirements
Component Requirements

Microsoft .NET Framework 4.6 (or later)

Windows platforms

64-bit editions of:

  • Windows 7
  • Windows 8.1
  • Windows 10
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016

If the appliance setting, TLS 1.2 Only is enabled, (Administrative Tools | Settings | Appliance | Appliance Information), ensure the desktop client also has TLS 1.2 enabled. If the client has an earlier version of TLS enabled, you will be locked out of the client and will not be able to connect to Safeguard for Privileged Passwords.


  • Internet Explorer security must be set to use TLS 1.0 or higher. Ensure the proper "Use TLS" setting is enabled on the Advanced tab of the Internet Options dialog (In Internet Explorer, go to Tools | Internet Options | Advanced tab).
  • To use FIDO2 two-factor authentication, you will need a web browser that supports the WebAuthn standard.

Desktop Player

See One Identity Safeguard for Privileged Sessions [version] Safeguard Desktop Player User Guide available at: One Identity Safeguard for Privileged Sessions - Technical Documentation, User Guide.

Web client system requirements

Table 3: Web requirements
Component Requirements
Web browsers

Desktop browsers:

  • Google Chrome 77 (or later)
  • Microsoft Internet Explorer 11 and Edge
  • Mozilla Firefox 69 (or later)

NOTE: To use FIDO2 two-factor authentication, you will need a web browser that supports the WebAuthn standard.

Mobile device browsers:

  • Apple iOS 13 (or later)
  • Google Chrome on Android version 77 (or later)

The web client is implemented for modern web browser technology, using:

  • HTML5
  • CSS
  • JavaScript

NOTE: If your browser lacks these required technologies, then use the desktop client.

Related Documents