One Identity recommends that you install One Identity Management Console for Unix, a separate One Identity product that provides a management console that is a powerful and easy-to-use tool that dramatically simplifies deployment of Safeguard Authentication Services agents to your clients. The management console streamlines the overall management of your Unix, Linux, and macOS hosts by enabling centralized management of local Unix users and groups and providing granular reports on key data and attributes.
Prior to installing Management Console for Unix, ensure your system meets the minimum hardware and software requirements for your platform.
| Component | Requirements |
|---|---|
| Supported platforms |
Can be installed on the following configurations:
|
| Server requirements |
The Management Console for Unix server requires Java 8 (also referred to as JRE 8, JDK 8, JRE 1.8, and JDK 1.8). |
| Managed Host Requirements |
Click www.oneidentity.com/products/safeguard-authentication-services/ to view a list of Unix, Linux, and Mac platforms that support Safeguard Authentication Services. Click www.oneidentity.com/products/privilege-manager-for-unix/ to review a list of Unix and Linux platforms that support Privilege Manager for Unix. Click www.oneidentity.com/products/privilege-manager-for-sudo/ to review a list of Unix, Linux, and Mac platforms that support Safeguard for Sudo. Considerations:
|
| Default memory requirement |
1024 MB NOTE: See JVM memory tuning suggestions in the One Identity Management Console for Unix Administration Guide for information about changing the default memory allocation setting in the configuration file. |
Safeguard Authentication Services must be able to communicate with Active Directory, including domain controllers, global catalogs, and DNS servers using Kerberos, LDAP, and DNS protocols. The following table summarizes the network ports that must be open and their function.
| Port | Function |
|---|---|
| 389 | Used for LDAP searches against Active Directory Domain Controllers. TCP is normally used, but UDP is used when detecting Active Directory site membership. |
| 3268 | Used for LDAP searches against Active Directory Global Catalogs. TCP is always used when searching against the Global Catalog. |
| 88 | Used for Kerberos authentication and Kerberos service ticket requests against Active Directory Domain Controllers. TCP is used by default. |
| 464 | Used for changing and setting passwords against Active Directory using the Kerberos change password protocol. Safeguard Authentication Services always uses TCP for password operations. |
| 53 | Used for DNS. Since Safeguard Authentication Services uses DNS to locate domain controllers, DNS servers used by the Unix hosts must serve Active Directory DNS SRV records. Both UDP and TCP are used. |
| 123 | UDP only. Used for time-synchronization with Active Directory. |
| 445 | CIFS port used to enable the client to retrieve configured group policy. |
Note: Safeguard Authentication Services, by default, operates as a client, initiating connections. It does not require any firewall exceptions for incoming traffic.
In preparing for your Safeguard Authentication Services upgrade, One Identity recommends that you install or upgrade Management Console for Unix first. This provides a management console that is a powerful and easy-to-use tool that dramatically simplifies deployment, enables management of local Unix users and groups, provides granular reports on key data and attributes, and streamlines the overall management of your Unix, Linux, and macOS hosts.
Note: Of course, you can install Safeguard Authentication Services without using Management Console for Unix. For more information, see Upgrade client components manually. However, for the purposes of the examples in this guide, it is assumed that you will install and configure the Safeguard Authentication Services Unix agent components by means of Management Console for Unix.
The process for upgrading Management Console for Unix from an older version is similar to installing it for the first time. The installer detects an older version of the console and automatically upgrades the components.
Note: The procedures in this topic assume you have Management Console for Unix 2.0.x (or later) installed.
Before you begin the upgrade procedure, close the console and make a backup of your database, as explained in step 1.
To upgrade Management Console for Unix
Management Console for Unix uses a HSQLDB (Hyper Structured Query Language Database) to store its data such as information about the hosts, settings, users, groups, and so forth.
Refer to Database Maintenance in the online help for more information about the database locations and filenames.
Once you backup the database files, you are ready to start the upgrade.
When the installer detects a previous version of the management console is already installed, it asks if you want to continue.
The installation wizard uninstalls the old version and configures the server database and service.
Note: After an upgrade from any version of Management Console for Unix, it is important to re-profile all managed hosts.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
