The simplest implementation of AuthMinder typically provides strong authentication internally for a small user base. It consists of all the AuthMinder components and Web applications installed on a single system. The database can be on the same system where AuthMinder is installed, or on a different system.
Note: See "Planning the Deployment" in the CA AuthMinder Installation and Deployment Guide for more information on this type of deployment.
The following table summarizes the typical characteristics of this deployment type:
|
Characteristic |
Details |
|---|---|
|
Deployment Type |
|
|
Geographic Expanse |
Typically restricted to a single location |
|
Deployment Requirements |
Ease of implementation and management |
In case of small deployments, most of the default settings will work out-of-the-box. Because this is a single-organization system, you can use the Default Organization, which is created automatically, when you initialize the system instead of setting up a new organization. As a result, you might not need OAs either. You, then, only need to create the required GAs and UAs.
A quick overview of the steps to set up and start managing strong authentication for your users is:
Note: See "Deploying AuthMinder on a Single System" in the CA AuthMinder Installation and Deployment Guide for more information on installing AuthMinder, deploying the WAR files, and performing other post-installation tasks.
Note: See "Bootstrapping the System" in the CA AuthMinder Installation and Deployment Guide for more information.
See "Creating Administrators" for more information.
See "Managing Global AuthMinder Configurations" for more information.
See "Creating Users" for more information.
With this your system is set for administration. You can now manage the system ("Managing AuthMinder Server Instances"), administrators ("Managing Administrators"), and users ("Managing Users and Their Credentials").
|
Copyright © 2013 CA.
All rights reserved.
|
|