On Networking, view and configure the primary network interface, and if applicable, a proxy server to relay web traffic, and the sessions network interface.
It is the responsibility of the Appliance Administrator to ensure the network interfaces are configured correctly.
|
CAUTION: For AWS or Azure, network settings user interfaces are read-only. Network settings configured by the AWS or Azure Administrator. Changing the internal network address on a clustered appliance will break the cluster and require the appliance to be unjoined/rejoined. |
(web client) To modify the networking configuration settings
- Click Settings on the left. The Settings: Appliance page displays.
- Click Networking to configure the appliance.
- Continue to the Network settings
(desktop client) To modify the networking configuration settings
- Navigate to Administrative Tools | Settings | Appliance | Networking.
- Click the Edit icon next to the Network Interface or Proxy Server heading to edit or configure the network properties.
- Network settings
Network settings
Complete the network settings. For more information, see Modifying the IP address.
Network Interface X0 (primary interface)
Proxy Server X0
The Proxy Server X0 settings must be configured if your company policies do not allow devices to connect directly to the web. Once configured, Safeguard for Privileged Passwords uses the configured proxy server for outbound web requests to external integrated services, such as Starling.
NOTE: Only HTTP web proxy is supported.
Property |
Description |
---|---|
Proxy URI |
The IP address or DNS name of the proxy server. |
Port |
The port number used by the proxy server to listen for HTTP requests. Value: Integer from 1 to 65535. NOTE: If different ports are specified in the proxy URI and the Port field, the Port field takes precedence. |
Username |
The user name used to connect to the proxy server. NOTE: The username and password are only required if your proxy server requires them to be specified. |
Password |
The password required to connect to the proxy server. NOTE: The username and password are only required if your proxy server requires them to be specified. |
Modifying the IP address
You can change the IP address of an SPP Appliance as long as the other appliances in the SPP cluster are able to see the new subnet.
It is recommended you use the procedure below in a test environment and then deploy the steps in production. Allow plenty of time for the IP address to change. The operation will take several minutes to complete before the cluster has adjusted to the change.
- Ensure you are using Safeguard for Privileged Passwords2.4 or above.
- Before changing the X0 IP address, make a backup.
- Generate a support bundle on the appliance you plan to modify the IP address on. Start with the replica first.
- The desktop client will give guidance on screen as you wait for the changes to be completed.
- After the X0 IP address change, verify clustering is working. It is recommended you change some data on the primary and verify it appears on the replica by logging on to the replica with the desktop client.
- Repeat step 3, 4, and 5 for the other replicas.
- Once the replicas are changed, proceed with the Primary.
Safeguard for Privileged Sessions (SPS) IP address change
|
CAUTION: When SPP and SPS are joined and then the IP address of either the SPS cluster master (Central Management role) or the SPP primary appliance are changed, then the SPP/SPS join will need to be redone. See the information that follows. |
- Use the following information in the SPS documentation to understand SPS cluster roles, settings, and IP address updating.
- Cluster roles: Assigning roles to nodes
-
Network settings: Setting SPS network interface and naming settings, including IP addresses
- Building a cluster: Assigning the Central Management node in a cluster (which cannot be undone) and then join other nodes
-
Assigning roles to nodes in your cluster: Assigning roles, including the Central Management role, to nodes in a cluster
-
Updating the IP address of a node in a cluster: Updating the IP address of SPS Managed Nodes
- Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster: Setting up SPS so, to handle nodes if the primary node stops functioning
- If the IP address is changed, you must rejoin the cluster. For more information, see Joining SPS to SPP.
- Once the SPS IP addresses are successfully changed, you will need to delete the session connection in the SPP settings and rejoin the SPS cluster master to the SPP primary. For more information, see SPP and SPS sessions appliance join guidance.