The following sections explain the basic management tasks of .
For basic management tasks (reboot and shutdown, disabling traffic), see Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown.
For managing a High Availability cluster, see Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster.
For instructions on upgrading SPS, see Upgrading One Identity Safeguard for Privileged Sessions (SPS).
For instructions on accessing SPS through console and SSH, see Accessing the One Identity Safeguard for Privileged Sessions (SPS) console.
For enabling sealed mode (which disables basic configuration changes from a remote host), see Sealed mode.
For information on configuring the out-of-band (IPMI) interface, see Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS).
For managing certificates used on SPS, see Managing the certificates used on One Identity Safeguard for Privileged Sessions (SPS).
To reboot or shut down One Identity Safeguard for Privileged Sessions (SPS)
The Other node refers to the secondary node of a High Availability SPS cluster. For details on High Availability clusters, see Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster.
|
Caution:
|
Figure 85: Basic Settings > System > System Control — Performing basic management
Web sessions to the SPS interface are persistent and remain open after rebooting SPS, so you do not have to relogin after a reboot.
During the reboot process, SPS displays information about the progress of the reboot and any possible problems in the following places:
On the web interface of SPS, at any of the Listening addresses configured at Basic settings > Local Services > Web login (admin and user). (After booting, you are directed to the login screen of SPS.)
On the console, which you can monitor with IPMI (ILOM) or console access.
The information displayed in the browser and on the console is the same.
The following describes how to temporarily disable some or all of the controlled traffic to the protected servers.
Figure 86: Basic Settings > System > Traffic control — Disabling the controlled traffic
|
Caution:
Disabling traffic that way is only temporary. Connections will be enabled again after committing any other change from the SPS web interface. For details on how to permanently disable a type of traffic, see Disabling controlled traffic permanently. |
Disabling the traffic affects only the traffic configured in the Connection policies, other traffic can pass SPS even if the all traffic is disabled. For details on configuring Connection policies, see General connection settings.
To temporarily disable some or all of the controlled traffic to the protected servers
Navigate to the Basic Settings > System > Traffic control.
To disable SSH traffic, click Stop in the SSH traffic field. Note that this also stops all other traffic forwarded in SSH, for example X11.
To disable RDP traffic, click Stop in the RDP traffic field.
To disable Telnet and TN3270 traffic, click Stop in the Telnet traffic field.
To disable VNC traffic, click Stop in the VNC traffic field.
To disable all types of traffic, click Stop in the All services field.
The System monitor displays the status of all types of traffic.
Disabling the traffic affects only the traffic configured in the Connection policies, other traffic can pass SPS even if the all traffic is disabled. For details on configuring Connection policies, see General connection settings.
To disable controlled traffic permanently
Figure 87: <Protocol name> Control > Global Options — Disabling the controlled traffic persistently
Navigate to the Global Options page of the traffic type you want to disable, for example to SSH Control > Global Options to disable SSH traffic.
Set the Traffic > Service field to disabled.
Click .
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy