The following is a list of issues known to exist at the time of release.
Issues may occur when launching telnet sessions after upgrading a Safeguard for Privileged Sessions appliance. If you are experiencing issues, ensure you have downloaded and installed the latest telnet plugin before contacting support. Additional information on configuring and supporting tenet sessions is also available on the telnet plugin site.
If session playback is failing for fully indexed sessions, the desktop player may need to be upgraded to 1.9.4 or greater.
SPS initiated sessions failing when using netbios name.
Workaround: Use the domain name.
Safeguard for Privileged Passwords allows you to manage access requests, approvals, and reviews for your managed accounts and systems.
- The web client consists of an end-user view and administrator view. The fully featured client exposes all of the functionality of Safeguard based on the role of the authenticated user.
- 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 linked to Safeguard for Privileged Passwords, session recording is handled via Safeguard for Privileged Session. The link is initiated from Safeguard for Privileged Sessions. For details about the link 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 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.
Table 3: Web kiosk requirements
|Web management console
- Apple Safari 16.0 for desktop (or later)
- Google Chrome 108 (or later)
- Microsoft Edge 108 (or later)
- Mozilla Firefox 108 (or later)
Platforms and versions follow.