CA AuthMinder UNIX Installation Guide › How to Plan the Deployment › Choosing a Deployment Model

Choosing a Deployment Model

As a part of Strong Authentication deployment, Strong Authentication Server is the primary component that you must install. You integrate your application with Strong Authentication Server by using the Java SDKs or Web Services that are shipped with Strong Authentication.

Strong Authentication also requires an SQL database for storing server configuration data, user-specific preferences, and usage data.

Typically, all Strong Authentication components are installed on a single system for development and simple testing. However, in production deployments and staging environments, Strong Authentication Server should be installed on its own system. The shipped SDKs or Web Services are installed on a different system or systems that contain the application that users log in to.

Strong Authentication is also shipped with Sample Application, which can be used to verify that Strong Authentication is installed properly and is able to perform user authentication. Sample Application also serves as a code sample for integrating Strong Authentication with your existing applications.

The high-level deployment types that are supported by Strong Authentication are:

• Single-System Deployment - For development or testing

  See "Deploying on a Single System" for more information.

• Distributed-System Deployment - For production or staging environments

  See "Deploying on Distributed Systems" for more information.

• High-Availability Deployment - For high availability and scalability, production, or staging environments

  See "Deploying in High-Availability Environment" for more information.