One Identity Safeguard for Privileged Sessions 5.9.0 - Administration Guide

Versions and releases of SPS

As of June 2011, the following release policy applies to One Identity Safeguard for Privileged Sessions:

• Long Term Supported or LTS releases (for example, SPS 4 LTS) are supported for 3 years after their original publication date and for 1 year after the next LTS release is published (whichever date is later). The second digit of the revisions of such releases is 0 (for example, SPS 4.0.1). Maintenance releases to LTS releases contain only bugfixes and security updates.

• Feature releases (for example, SPS 4 F1) are supported for 6 months after their original publication date and for 2 months after a succeeding Feature or LTS release is published (whichever date is later). Feature releases contain enhancements and new features, presumably 1-3 new features per release. Only the last feature release is supported (for example, when a new feature release comes out, the last one becomes unsupported in 2 months).

For a full description of stable and feature releases, open the SPS product page on the Support Portal and navigate to Product Life Cycle & Policies > Product Support Policies > Software Product Support Lifecycle Policy.

Accessing and configuring SPS

SPS has a web interface and is configured from a browser. The users of SPS can be authenticated using local, LDAP, or RADIUS databases. The privileges of users are determined by group memberships that can be managed either locally on SPS, or centrally in an LDAP database. Assigning privileges to groups is based on Access Control Lists (ACLs). It is also possible to match groups existing in the LDAP database to a set of SPS privileges. Access control in SPS is very detailed, it is possible to define exactly who can access which parts of the interface and of the stored data.

Figure 17: Authenticating the users of SPS

The Welcome Wizard and the first login

This chapter describes the initial steps of configuring SPS. Before completing the steps below, unpack, assemble, and power on the hardware. Connect interface 1 (labelled 1 or EXT) to the local network, or directly to the computer from which SPS will be configured.

The initial connection to SPS

SPS can be connected from a client machine using any modern web browser.

SPS can be accessed from the local network. Starting with version 3.1, SPS attempts to receive an IP address automatically via DHCP. If it fails to obtain an automatic IP address, it starts listening for HTTPS connections on the 192.168.1.1 IP address. Note that certain switch configurations and security settings can interfere with SPS receiving an IP address via DHCP. SPS accepts connections via its interface 1 (labelled 1 or EXT). For details on the network interfaces, see Network interfaces).

If SPS is listening on the 192.168.1.1 address, note that the 192.168.1.0/24 subnet must be accessible from the client. If the client machine is in a different subnet (for example, its IP address is 192.168.10.X), but in the same network segment, the easiest way is to assign an alias IP address to the client machine. Creating an alias IP on the client machine virtually puts both the client and SPS into the same subnet, so that they can communicate. To create an alias IP complete the following steps.

• For details on creating an alias IP on Microsoft Windows, see Creating an alias IP address (Microsoft Windows).

• For details on creating an alias IP on Linux, see Creating an alias IP address (Linux).

• If configuring an alias interface is not an option for some reason, you can modify the IP address of SPS. For details, see Modifying the IP address of SPS.