To install (and later configure) AuthMinder on Windows successfully, the user account that you plan to use for installation must belong to the Administrators group. Else, some critical steps in the installation, such as DSN creation and configuration and AuthMinder service creation, will not go through successfully, though the installation may get completed without any errors.
In a distributed scenario, you can distribute AuthMinder, Administration Console, Java SDKs, and Web Services on different systems. Typically, you install AuthMinder Server on the first system. Custom installation allows you to install only the selected components from the package. This option is recommended for advanced users.
Note: Before proceeding with the installation, ensure that all the prerequisite software are installed and the database is set up, as described in chapter, "Preparing for Installation".
Perform the following steps to install AuthMinder and related components:
The Welcome screen appears. It may take a few minutes for this screen to appear.
The License Agreement screen appears.
The installer now checks if any other CA product is installed on the computer.
If it does not find an existing CA product installation, then you will be prompted for an installation directory. In this case, the Installation Location screen appears.
If the installer detects an existing CA product installation, then you will not be prompted for an installation directory. The Installation Location Screen: Previous Installation Detected screen appears when an existing ARCOT_HOME was located on the computer.
Click Next to install in the specified directory.
The Installation Type screen appears.
The Component Selection screen appears.
For example, to install AuthMinder Server, Administration Console, and User Data Service (without the SDKs and the Sample Application) on the current system, you will need to:
The following table describes all components that are installed by the AuthMinder installer:
|
Component |
Description |
|---|---|
|
Arcot WebFort Authentication Server |
This option installs the core Processing engine (WebFort Server) that serves the following requests from SDKs, Administration Console, and web services:
In addition, this component also enables you to access the following Web services:
|
|
Arcot WebFort Java SDK and WS |
This option provides programming interfaces (in form of APIs and Web Services) that can be invoked by your application to forward authentication and user credential issuance requests to the AuthMinder Server. This package comprises the following sub-components:
Refer to chapter, "Configuring AuthMinder Java SDKs and Web Services" for more information on configuring these components. |
|
Arcot WebFort Sample Application |
This option provides Web-based interface for demonstrating the usage of AuthMinder Java APIs. In addition, it can also be used to verify if AuthMinder was installed successfully, and if it is able to perform credential management and authentication requests. |
|
Arcot Administration Console |
This option provides the Web-based interface for managing AuthMinder Server and authentication-related configurations. |
|
Arcot User Data Service |
This option installs UDS that acts as an abstraction layer for accessing different types of user repositories, such as relational databases (RDBMSs) and directory servers (LDAPs.) |
The Database Type screen appears.
Depending on the Database you selected, the corresponding Database Details screen appears.
Depending on the database that you selected, perform one of the following steps:
Perform the following tasks for MS SQL database access:
|
Field |
Description |
|---|---|
|
ODBC DSN |
AuthMinder Server uses the ODBC DSN to connect to the AuthMinder database. The recommended value to enter is arcotdsn. The installer creates the DSN using this value. |
|
Server |
The host name or IP address of the database server. If SQL server is deployed in Named Instance mode, then you must also enter a slash "\" followed by the instance name, refer to vendor documentation for more information on this. Default Instance Syntax: <Server Name> Example: demodatabase Named instance Syntax: <Server Name>\<instance name> Example: demodatabase\instance1 |
|
User Name |
The User Name that AuthMinder uses to access the database (SQL Server refers to this as login). This name is specified by the database administrator. Note: The User Name for the Primary and Backup DSN must be different. |
|
Password |
The password that AuthMinder uses to access the database. This password is specified by the database administrator. |
|
Database |
The name of the database that AuthMinder will access. |
|
Port Number |
The port on which the database server listens to the incoming requests. |
Perform the following tasks for IBM DB2 (UDB) database access:
|
Field |
Description |
|---|---|
|
ODBC DSN |
AuthMinder Server uses the ODBC DSN to connect to the AuthMinder database. The recommended value to enter is arcotdsn. The installer creates the DSN using this value. |
|
Server |
The host name or IP address of the database server. If the database is deployed in Named Instance mode, then you must also enter a slash "\" followed by the instance name, refer to vendor documentation for more information on this. Default Instance Syntax: <Server Name> Example: demodatabase Named instance Syntax: <Server Name>\<instance name> Example: demodatabase\instance1 |
|
User Name |
The User Name that AuthMinder uses to access the database. This name is specified by the database administrator. Note: The User Name for the Primary and Backup DSN must be different. |
|
Password |
The password that AuthMinder uses to access the database. This password is specified by the database administrator. |
|
Port Number |
The port on which the database server listens to the incoming requests. |
|
Database |
The name of the database that AuthMinder will access. |
Perform the following tasks for Oracle database access:
|
Field |
Description |
|---|---|
|
ODBC DSN |
AuthMinder Server uses the ODBC DSN to connect to the AuthMinder database. The recommended value to enter is arcotdsn. The installer creates the DSN using this value. |
|
User Name |
The User Name that AuthMinder uses to access the database. This name is specified by the database administrator. Note: The User Name for the Primary and Backup DSN should be different. |
|
Password |
The password that AuthMinder uses to access the database. This password is specified by the database administrator. |
|
Service ID |
The Oracle System Identifier that refers to the instance of the Oracle database running on the Oracle server. |
|
Port Number |
The port on which the database server listens to the incoming requests. |
|
Host Name |
The host name or the IP address of the computer where the Oracle server is available. Syntax: <Host Name or IP address> Example: demodatabase |
Perform the following tasks for MySQL database access:
|
Field |
Description |
|---|---|
|
ODBC DSN |
AuthMinder Server uses the ODBC DSN to connect to the AuthMinder database. The recommended value to enter is arcotdsn. The installer creates the DSN using this value. |
|
Server |
The host name or IP address of the database server. If SQL server is deployed in Named Instance mode, then you must also enter a slash "\" followed by the instance name, refer to vendor documentation for more information on this. Default Instance Syntax: <Server Name> Example: demodatabase Named instance Syntax: <Server Name>\<instance name> Example: demodatabase\instance1 |
|
User Name |
The User Name that AuthMinder uses to access the database (SQL Server refers to this as login). This name is specified by the database administrator. Note: The User Name for the Primary and Backup DSN must be different. |
|
Password |
The password that AuthMinder uses to access the database. This password is specified by the database administrator. |
|
Database |
The name of the database that AuthMinder will access. |
|
Port Number |
The port on which the database server listens to the incoming requests. |
The Encryption Configuration screen appears. This screen is used to select the encryption mode and set the information used for encryption.
If you want to change the value of the master key after the installation, then you must regenerate the securestore.enc file with a new master key value. For more information, see the CA AuthMinder Administration Guide.
Note: The following options are enabled only if you choose to Configure HSM.
For Luna (cryptoki.dll) and for nCipher netHSM (cknfast.dll), specify the absolute path and name of the file.
Click Next to continue.
The Pre-Installation Summary screen appears. This screen lists the product name, installation folder, type of installation, and components that are selected.
The Microsoft Visual C++ 2010 x86 Redistributable Setup screen appears. This screen appears only if the current system where you are installing AuthMinder does not have Microsoft Visual C++ 2010 x86.
The Installation Progress screen appears. This might take a few seconds. After some time the Installation Is Complete screen appears.
The Installing Arcot WebFort screen appears. This might take several minutes. After some time the Installation Complete screen appears.
After installation, you can access the installation log file (Arcot_WebFort_Install_<mm_dd_yyyy_hh_mm_ss>.log) in the <install_location> directory. For example, if you had specified the C:\Program Files directory as the installation directory, then the installation log file is created in the C:\Program Files directory.
If the installation fails for some reason, then error messages are recorded in this log file.
|
Copyright © 2013 CA.
All rights reserved.
|
|