Once you have created a node package file, you must transfer it to the target host. RSA recommends that you transfer the package through a secure network or by removable media.
Note the location on the target host where you copy the package. This information, along with the master password, is required during installation.
Performing an Installation
You can perform an installation using the GUI or the command line interface.
Use the GUI-based installer if you prefer standard graphical screens to assist you through the process. If you prefer a command line interface, you can use the command line installer.
Installation time varies depending on system speed and memory. Make sure that you allow at least one hour to perform the installation.
Important: Make sure that the primary or replica instance where you created the node package is running before you begin the installation.
To install Authentication Manager:
1. Locate and launch the installer for your platform using the information in the following table.
Note: For the command line interface, you must add the -console option to the command. The command line installer displays navigation prompts with instructions on how to proceed or select options.
2. On the Welcome screen, click Next.
3. If you are installing Authentication Manager on a Solaris or Linux operation system, specify the local user.
Note: This cannot be root user. RSA recommends that you set up an account specifically for the Authentication Manager installation that can be accessed by any administrator. Do not use a personal account.
4. Respond to the prompts for Select Region and License Agreement.
Platform Location Command
Windows 32-bit auth_mgr\win32-x86 setup.exe
Windows 64-bit auth_mgr\windows-x86_64 setupwinAMD64.exe
Linux 32-bit auth_mgr/linux-x86 setupLinux.sh
Linux 64-bit auth_mgr/linux-x86_64 setupLinux64.sh Solaris 10-sparc auth_mgr/solaris-sparc_64 setupSolaris.sh
RSA Authentication Manager 7.1 Installation and Configuration Guide
64 5: Installing a Server Node
5. Select Server Node.
Important: At this point, the installer informs you if there are unmet or missing requirements and prerequisites for installation and offers you the option to continue anyway. Select Continue anyway only if you are directed to do so by RSA Customer Support or if you are certain that you want to accept the risk.
Important: In most cases, once you have installed Authentication Manager, you cannot change the installation type later on, unless you uninstall
Authentication Manager and reinstall it using the appropriate installation type.
Before you uninstall and reinstall, be sure to back up the Authentication Manager database, and restore the databases after reinstalling.
6. Verify the directory name, or click Browse to install Authentication Manager in a different directory.
Note: This location must be the same directory as the one where you installed the primary or replica instance.
7. The installer displays the hostname and IP address that will be used for installation. Verify that this information is correct, and click Next.
Note: If the machine has multiple network interface cards, make sure that the IP address and hostname that you specify during installation belong to the interface you want to use. The default is for the primary network adapter. The RSA Security Console listens only to the IP address that you specify. Failure to verify the IP address and hostname results in installation or server startup problems.
8. Click Browse to locate the folder that contains your Authentication Manager license file, server key, and certificate files. The license allows you access to certain functionality and limits the number of users that can be registered. The server key and certificate are used to verify (authenticate) the identity of the server. Select the folder, and click Next.
Note: When you select the folder, the filenames do not display and the folder appears to be empty.
9. Verify the license information, and click Next.
10. When prompted, enter the following information:
• The location of the node package file that you created and transferred from the primary or replica instance. If you have not finished these tasks, see
“Preparing to Install a Server Node” on page 61.
• The master password for the primary instance, specified at primary installation time.
11. Review the summary screen, verifying the features you have selected and the disk space required.
12. To begin copying Authentication Manager files, click Install.
The installer begins copying files and displays a progress indicator.
13. Click Finish to close the installer.
If you encounter any problems installing Authentication Manager, see Chapter 13,
“Troubleshooting.”
Rebalancing Contact Lists
After you add a server node, you must rebalance the contact lists in the primary instance Security Console. This updates references to the new server nodes.
Note: If the servers are restarted, the references to the new server nodes are automatically updated.
To update your contact lists:
1. Click Access > Authentication Agents > Authentication Manager Contact List > Automatic Rebalance.
2. Click Rebalance.
3. Perform an authentication.
Securing Backup Files
The installer automatically backs up a list of important files to
RSA_AM_HOME/backup. Immediately after installation, copy the backup directory to a secure location.
Important: For highest security, store SYSTEM.SRK, included in your backup folder, on removable media. Retrieve this private key only for disaster recovery. You may want to consider making an additional backup of this data that you store in an alternate, secure location.
RSA Authentication Manager 7.1 Installation and Configuration Guide
66 5: Installing a Server Node