The following table provides a list of supported platforms for Privilege Manager for Unix clients.
Table 3: Linux supported platforms — server and client
|
Amazon Linux |
AMI, 2 |
x86_64 |
|
CentOS Linux |
6, 7, 8 |
Current Linux architectures: s390x, PPC64, PPC64le, x86, x86_64, AARCH64 |
|
Debian |
Current supported releases |
x86_64, x86, AARCH64 |
|
Fedora Linux |
Current supported releases |
x86_64, x86, AARCH64 |
|
OpenSuSE |
Current supported releases |
x86_64, x86, AARCH64 |
|
Oracle Enterprise Linux (OEL) |
6, 7, 8 |
Current Linux architectures: s390x, PPC64, PPC64le, x86, x86_64, AARCH64 |
|
Red Hat Enterprise Linux (RHEL) |
6, 7, 8 |
Current Linux architectures: s390x, PPC64, PPC64le, x86, x86_64, AARCH64 |
|
SuSE Linux Enterprise Server (SLES)/Workstation |
11 SP4, 12, 15 |
Current Linux architectures: s390x, PPC64, PPC64le, x86, x86_64, AARCH64 |
|
Ubuntu |
Current supported releases |
x86_64, x86, AARCH64 |
Table 4: Unix and Mac supported platforms — client
|
Apple MacOS |
10.15 or later |
x86_64, ARM64 |
|
FreeBSD |
12.x, 13.x |
x32, x64 |
|
HP-UX |
11.31 |
PA, IA-64 |
|
IBM AIX |
6.1 TL9, 7.1 TL3, 7.2 |
Power 4+ |
|
Oracle Solaris |
10 8/11 (Update 10), 11.x |
SPARC, x64 |
Before installing Privilege Manager for Unix 7.2 , ensure that your system meets the following minimum hardware and software requirements.
NOTE: Beginning with version 7.2 , Privilege Manager for Unix supports only Linux-based systems for Privilege Manager for Unix policy servers.
Table 5: Hardware and software requirements
| Operating systems |
See Supported platforms to review a list of platforms that support Privilege Manager for Unix clients. |
| Disk space |
80 MB of disk space for program binaries and manuals for each architecture.
Considerations:
- At a minimum, you must have 80 MB of free disk space. The directories in which the binaries are installed must have sufficient disk space available on a local disk drive rather than a network drive. Before you install Privilege Manager for Unix, ensure that the partitions that will contain /opt/quest have sufficient space available.
-
Sufficient space for the keystroke logs, application logs, and event logs. The size of this space depends on the number of servers, the number of commands, and the number of policies configured.
-
The space can be on a network disk drive rather than a local drive.
- The server hosting Privilege Manager for Unix must be a separate machine dedicated to running the pmmasterd daemon.
|
| SSH software |
You must install and configure SSH client and server software on all policy server hosts.
You must enable access to SSH as the root user on the policy server hosts during configuration of the policy servers. Both OpenSSH 4.3 (and later) and Tectia SSH 6.4 (and later) are supported. |
| Processor |
Policy Servers: 4 cores |
|
RAM |
Policy Servers: 8GB |
Upgrade and compatibility
Privilege Manager for Unix supports a direct upgrade installation from version 6.0 and higher. The Privilege Manager for Unix software in this release is provided using platform-specific installation packages. For more information on upgrading, see the One Identity Privilege Manager for Unix Administration Guide.
One Identity recommends that:
- You upgrade your policy server (Master) systems before agents, and that a policy server is run at the same or higher level than agents.
- All policy server systems and agents are upgraded to the latest version to take advantage of all new features.
The upgrade process will create symbolic links to ensure that your existing paths function correctly.
Use of the Privilege Manager for Unix clients (pmrun and pmshells) with a policy server in Sudo policy mode is not supported.
Although licenses are allocated on a per-agent basis, you install licenses on Privilege Manager for Unix policy servers.
No special commands are required to register or license the clients with policy servers. Hosts using the Privilege Manager for Unix agents are automatically granted a license once a request is received on the Privilege Manager for Unix policy server by means of the pmrun command.
To install a license file
- Copy the .dlv license file to the policy server.
- To install the license, run:
# /opt/quest/sbin/pmlicense -l <license_file>
This command displays your currently installed license and the details of the new license to be installed.
- When it asks, "Would you like to install the new license (Y/N) [Y]?", press Enter, or type: Y
- If there are other policy servers configured in your policy server group, it forwards the license configuration to the other servers.
See the Privilege Manager for Unix Administration Guide for more information about the syntax and usage of the pmlicense command.
NOTE: Due to a change in the communication protocol, using 7.1 or later clients and servers with 7.0 clients and servers is not supported. One Identity recommends you upgrade all of your 7.0 installations to 7.1 or later versions. Installations of release 6.x are not affected and can still be used with 7.1.
