The simplest implementation of RiskMinder typically provides adaptive authentication for a small user base. It consists of all the RiskMinder components and Web applications installed on a single system. The database can be on the same system where RiskMinder is installed, or on a different system.
Note: See "Planning the Deployment" in the CA RiskMinder Installation and Deployment Guide for more information on this type of deployments.
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 OA accounts either. You, then, only need to create the required GA and UA accounts.
The quick overview of the steps to set up and start managing strong authentication for your users is:
Note: See "Deploying RiskMinder on a Single System" in the CA RiskMinder Installation and Deployment Guide for more information on installing RiskMinder, deploying the WAR files, and performing other post-installation tasks.
Note: See "Bootstrapping the System" in the CA RiskMinder Installation and Deployment Guide for more information.
See "Creating Administrators" for more information.
See "Managing Global Configurations" for more information.
See "Creating Users" for more information.
With this, your system is set for risk evaluation. You can now manage the system ("Managing RiskMinder Server Instances"), administrators ("Managing Administrators"), and users ("Managing Users").
|
Copyright © 2013 CA.
All rights reserved.
|
|