Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 5.9.0 - Administration Guide

Preface Introduction The concepts of SPS The Welcome Wizard and the first login Basic settings User management and access control Managing SPS
Controlling SPS: reboot, shutdown Managing Safeguard for Privileged Sessions clusters Managing a high availability SPS cluster Upgrading SPS Managing the SPS license Accessing the SPS console Sealed mode Out-of-band management of SPS Managing the certificates used on SPS
General connection settings HTTP-specific settings ICA-specific settings RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search (classic) interface Using the Search interface Searching session data on a central node in a cluster Advanced authentication and authorization techniques Reports The SPS RPC API The SPS REST API SPS scenarios Troubleshooting SPS Configuring external devices Using SCP with agent-forwarding Security checklist for configuring SPS Jumplists for in-product help Third-party contributions About us

Managing the SPS license

Information of the current license of SPS is displayed on the Basic Settings > System > License page. The following information is displayed:

Figure 104: Basic Settings > System > License — Updating the license

  • Customer: The company permitted to use the license (for example Example Ltd.).

  • Serial: The unique serial number of the license.

  • Limit type:

    • Host: Limits the number of servers (individual IP addresses) that can be connected through SPS.

    • Session: Limits the number of concurrent sessions (parallel connections) that can pass through SPS at a time (for example 25). SPS will reject additional connection requests until an already established connection is closed.

  • Limit: The actual value of the session or host limit. To list which hosts SPS counts against this limit, click the on the value of the limit.

  • Valid: The period in which the license is valid. The dates are displayed in YYYY/MM/DD format.

The full text of the End User License Agreement is also displayed here.

SPS starts sending automatic alerts daily, 60 days before the license expires. An alert is sent also when the number of protected servers exceeds 90% of the limit set in the license.

Updating the SPS license


The SPS license must be updated before the existing license expires or when you purchase a new license.


To update the license, complete the following steps:


Before uploading a new license, you are recommended to backup the configuration of SPS. For details, see Exporting the configuration of SPS.

  1. Navigate to Basic Settings > System > License.

  2. Click Browse and select the new license file.


    It is not required to manually decompress the license file. Compressed licenses (for example .zip archives) can also be uploaded.

  3. Click Upload, then Commit.

  4. Caution:

    This step terminates all controlled connections going through SPS. Disconnect your clients from the protected servers before proceeding.

    To activate the new license, navigate to Traffic control > All services and click Restart.

Accessing the SPS console

This section describes how to use the console menu of SPS, how to enable remote SSH access to SPS, and how to change the root password from the web interface.

Using the console menu of SPS

Connecting to the One Identity Safeguard for Privileged Sessions locally or remotely using Secure Shell (SSH) allows you to access the console menu of SPS. The console menu provides access to the most basic configuration and management settings of SPS. It is mainly used for troubleshooting purposes, the primary interface of SPS is the web interface.

The console menu is accessible to the root user using the password set during completing the Welcome Wizard.

Figure 105: The console menu

The console menu provides allows you to perform the following actions:

  • Access the local core and boot shells. This is usually not recommended and only required in certain troubleshooting situations. Select the boot/core shell's keyboard layout for the local console. This will not affect the keyboard layout if you have accessed the shell via SSH.

    The boot firmware boots up SPS, provides high availability support, and starts the core firmware. The core firmware, in turn, handles everything else: provides the web interface, manages the connections, and so on.

  • Select the active firmware, and delete unneeded firmwares. Accessing the firmware management is useful if after an update the new firmware does not operate properly and the web interface is not available to activate the previous firmware.

  • Start backup processes.

  • Change the passwords of the root and admin users.

  • Access the network-troubleshooting functions and display the available log files. If the web interface is inaccessible, it can be the result of an internal locking error. To resolve this issue, delete the lock files. After deletion, they are archived, and included in the support bundle if they are not older than 30 days. To create a support bundle, if the web interface is inaccessible, select Create support bundle.


    If deleting the lock files did not resolve the issue, contact our Support Team.

  • Reboot and shutdown the system.

  • Enable and disable sealed mode. For details, see Sealed mode.

  • Set the IP address of the HA interface.


Note that logging in to the console menu automatically locks the SPS interface, meaning that users cannot access the web interface while the console menu is used. The console menu can be accessed only if there are no users accessing the web interface. The connection of web-interface users can be terminated to force access to the console menu.

Related Documents