Safeguard Authentication Services 4.2 - Installation Guide

Installing and joining from the Unix command line

While you can use Management Console for Unix to install and configure Authentication Services as explained in Installing and configuring Authentication Services, you can also manually install the Authentication Services agent on each Unix, Linux, or Mac OS X host from the command line.

This section walks you through the process of installing the Authentication Services Unix agent directly from the command line. For information about installing, upgrading, and uninstalling the Authentication Services agent on supported platforms in an enterprise environment using platform package management tools, refer to Enterprise package deployment.

Before installing and configuring the Authentication Services Unix agent, One Identity recommends that you run the preflight tool to check a host's suitability to run Authentication Services. After you determine that the Unix host is ready, run the Authentication Services installation script, install.sh, to install the Unix/Linux agent.

The Authentication Services pre-installation diagnostic tool

One Identity provides the preflight utility to check a host's suitability to run Authentication Services by verifying a number of environmental considerations necessary for joining an Active Directory domain.

This utility obtains answers to the following questions:

• Does Authentication Services support the host on which this utility is being run?
• Are the operating system and any patches at requisite levels?
• Is there at least one visible domain controller (DC)?
• Are global catalogs available on any of the domain controllers?
• Are all services needed by Authentication Services available?
• Is an Authentication Services application configuration set up on the target domain?

The preflight command-line utility performs the following verifications.

Install checks:

• Check for supported operating system and correct operating system patches.
• Check for sufficient disk space to install Authentication Services.

Join checks:

• Check that the hostname of the system is not localhost.
• Check if the name service is configured to use DNS.
• Check resolv.conf for proper formatting of name service entries and that the host can be resolved.
• Check for a name server that has the appropriate DNS SRV records for Active Directory.
• Detect a writable domain controller with UDP port 389 open.
• Detect Active Directory site, if available.
• Check if TCP port 464 is open for Kerberos kpasswd.
• Check if UDP port 88 and TCP port 88 are open for Kerberos traffic.
• Check if TCP port 389 is open for LDAP.
• Check for a global catalog server and if TCP port 3268 is open for communication with global catalog servers.
• Check for a valid time skew against Active Directory.
• Check for the Authentication Services application configuration in Active Directory.

Post-join checks:

• Check if TCP port 445 is open for Microsoft CIFS traffic.

You can find the preflight.sh script at the root of the ISO. This script runs the correct preflight version for your system.

The most important options and arguments to preflight are:

• domain-name

  The domain you want to join with Authentication Services.

• -u username

  An identity with administrator rights for the Active Directory domain you want to join.

Running preflight

To run preflight

1. Mount the Authentication Services distribution media.
2. Enter the following command at the root of the Authentication Services ISO:

   # ./preflight.sh -u Administrator example.com

   where Administrator is your user name and example.com is the name of your domain.

   By default, preflight outputs the results of the verifications for the three types of checks (Install checks, Join checks, and Post-join checks) to the console. Run the preflight utility with the --verbose option to obtain detailed information about the various checks in those categories.

   The last line of the output tells you whether you are ready to continue deploying Authentication Services.

   If you did not get a Preflight Checks complete with status Success message, correct any failures indicated before continuing with the Authentication Services installation. Be aware of any "Advisories" that it returns, as they may effect your ability to install or join.

The Authentication Services install script

Follow the steps in this topic if you are installing a Authentication Services 4.2 for the first time; that is, if you are not upgrading from VAS 3.5.

The Authentication Services installation script, install.sh, installs Authentication Services, joins the domain, and allows you to install licenses. You can run the install script in interactive mode by using the -i option. This provides you with a menu of valid operations to perform, including Running preflight.

You can also automate the installation process by running install.sh in "unattended" mode using -q option. In this mode you may specify a set of commands for the script to perform.

install.sh --help