Exclusively for troubleshooting purposes, you can access the One Identity Safeguard for Privileged Sessions (SPS) host using SSH.
Completing the Welcome Wizard automatically disables SSH access to SPS. Re-enabling it allows you to connect remotely to the SPS host and login using the root user. The password of the root user is the one you provided in the Welcome Wizard. For details on how to change the root password from the web interface, see Changing the root password of One Identity Safeguard for Privileged Sessions (SPS).
The following encryption algorithms are configured on the local SSH service of SPS:
-
Key exchange (KEX) algorithms:
diffie-hellman-group-exchange-sha256
-
Ciphers:
aes256-ctr,aes128-ctr
-
Message authentication codes:
hmac-sha2-512,hmac-sha2-256
SSH access is, by default, protected against brute-force attacks: after 20 unsuccessful login attempts, the offending IP is blocked from accessing the SSH service for ten minutes.
You can turn off brute force protection by unselecting the Protect against brute-force attacks option for the SSH server.
To enable SSH access to the SPS host
-
Navigate to Basic Settings > Local Services > SSH server.
Figure 141: Basic Settings > Local Services > SSH server — Enabling remote SSH access to SPS
-
Select the Enable option.
NOTE: Remote SSH access is automatically disabled if Sealed mode is enabled. For details, see Sealed mode.
-
Choose the authentication method for the remote SSH connections.
-
To enable password-based authentication, select the Enable password authentication option.
-
To enable public-key authentication, click 
in the Authorized keys field, click 
and upload the public keys of the users who can access and manage SPS remotely via SSH.
SPS allows you to use the following SSH host keys:
-
RSA (ssh-rsa), which is the most widely used public-key algorithm for the SSH key. In SPS, uploading RSA SSH host keys are supported in PKCS #1 PEM, PKCS #8 PEM, OpenSSH (openssh-key-v1), and PuTTY private key formats.
NOTE:
TIP: One Identity recommends using 2048-bit RSA keys (or stronger).
-
Ed25519 (ssh-ed25519), which offers a better security and faster performance compared to RSA.
In SPS, uploading Ed25519 SSH host keys are supported in PKCS #8 PEM, OpenSSH (openssh-key-v1), and PuTTY private key formats.
-
ECDSA NIST P-256 (ecdsa-sha2-nistp256), which is a variant of the Digital Signature Algorithm (DSA). In SPS, uploading ECDSA SSH host keys are supported in SEC1 PEM, PKCS #8 PEM, OpenSSH (openssh-key-v1), and PuTTY private key formats.
You can have multiple SSH server host keys on SPS for the same server, however, you cannot set more than one key for each type. For example, you can keep your old RSA SSH key and generate a new Ed25519 key but you cannot set two RSA keys.
-
Choose an address and a port for the SSH server in the Listening addresses section.
The available addresses correspond to the interface addresses configured in Basic Settings > Network > Interfaces. Only IPv4 addresses can be selected.
To add multiple addresses, click .
-
(Optional) To permit SSH acces only from selected subnets or IP addresses, select Restrict clients, click and enter the IP address and netmask of the allowed clients.
Use an IPv4 address.
To add multiple addresses, click .
-
Click 
.
The root password is required to access One Identity Safeguard for Privileged Sessions (SPS) locally, or remotely via an SSH connection. Note that the password of the root user can be changed from the console menu as well. For details, see Accessing the One Identity Safeguard for Privileged Sessions (SPS) console.
To change the root password of SPS
-
Navigate to Basic Settings > Management > Change root password.
Figure 142: Basic Settings > Management > Change root password — Changing the root password of SPS
-
Enter the new password into the New root password and Confirm password fields.
NOTE: SPS accepts passwords that are not longer than 150 characters and supports the following characters:
-
Click .
In some cases, uploading large files over HTTP is not possible. In such cases, you can update the firmware using SSH.
|
|
Caution:
One Identity recommends that you update the firmware by using the One Identity Safeguard for Privileged Sessions (SPS) web interface (for more information, see Upgrading One Identity Safeguard for Privileged Sessions (SPS)). Update the SPS firmware using SSH only if you cannot update it using the web interface. Consider that updating the firmware using SSH may not be supported in later versions of SPS. |
To update the firmware using SSH
-
Download the firmware file to your computer.
-
Log in to SPS remotely using SSH, and select Shells > Core shell from the console menu.
-
Copy the firmware to the SPS host (for example, into the /root/ directory).
If you are copying the firmware to SPS using SCP and you issue the copy command on the client side and not within the core firmware, the root directory of the core firmware is: /mnt/firmware/root
-
Install the firmware: /opt/nnx-scb/bin/firmwarectl install <path-to-firmware>
This command installs the firmware into the first empty slot, and returns the value of the slot where the firmware has been installed.
-
Check if you can upgrade to the new firmware, and resolve any errors before you continue: /opt/nnx-scb/bin/firmwarectl precheck <slot-number-of-the-firmware>
In the returned values, "exitcode": 0 means that the precheck has finished without any errors. The "exitcode": 1 return value means that errors have occurred, and the contents of "output": [] gives you a clue as to what is causing the problem.
-
Activate the new firmware: /opt/nnx-scb/bin/firmwarectl activate <slot-number-of-the-firmware>
Using the /opt/nnx-scb/bin/firmwarectl list command, you can check whether activation has been successful. In the returned values, look for your slot number and the value of "active":. If activated successfully, the value is true. For example:
...
"slot": 3,
"precheck": true,
"active": true,
"boot_link": "mnt/boot-firmware/slot3",
"core_link": "mnt/firmware/slot3",
"branch": "5.6",
"version": "5.6.0a",
"current": false,
...
-
Reboot SPS: xcbclient self xcb_do_reboot
-
If the upgrade is successful, delete any unused firmware: /opt/nnx-scb/bin/firmwarectl delete <slot-number-of-unused-firmware>
-
As you do not need it anymore, delete the firmware file you uploaded to SPS: rm -fv /root/<firmware-file-you-uploaded>
For manual archiving, or to migrate it to another One Identity Safeguard for Privileged Sessions (SPS) unit, you can export/import the configuration of SPSfrom the console using the /opt/scb/bin/configbundle.py script.
NOTE: You must run the /opt/scb/bin/configbundle.py script using the root user.
NOTE: The configuration of your SPS may contain sensitive information. Make sure you delete any configuration export files that are not needed anymore.
To export/import the configuration of SPS from the console
-
Execute the following command to export the configuration of your SPS:
/opt/scb/bin/configbundle.py create --bundle /<my destination folder>/bundle.tar.gz
Where:
-
/opt/scb/bin/configbundle.py: The script you execute to export the configuration.
-
create: The option that lets you export a configuration.
-
--bundle: The option used to specify the bundle file.
-
/<my destination folder>/bundle.tar.gz: The path to the file where you wish to export the configuration.
Replace <my destination folder> with the name of the folder where you wish to store the exported configuration.
-
Execute the following command to import the configuration of your SPS:
/opt/scb/bin/configbundle.py import --bundle /<my destination folder>/bundle.tar.gz
Where:
-
/opt/scb/bin/configbundle.py: The script you execute to import the configuration.
-
import: The option that lets you import a configuration.
-
--bundle: The option used to specify the bundle file.
-
/<my destination folder>/bundle.tar.gz: The path to the file from which you wish to import the configuration.
Replace <my destination folder> with the name of the folder where your configuration export file is stored.
