Previous Topic: For Simple DeploymentsNext Topic: Getting Started


For Complex Deployments

In larger enterprises, where the deployments are complex and high availability is a must, RiskMinder can be implemented to provide adaptive authentication for the large user base, as well as for the administrators who manage the system. In these deployments, RiskMinder components are installed on different servers. This is done for security, performance, high availability, and to enable multiple applications to use the adaptive-authentication capability.

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

  • Complex medium to large businesses
  • Enterprise deployments
  • Staging deployments

Geographic Expanse

Distributed across the globe

Deployment Requirements

  • Ease of implementation and management
  • Global availability
  • High availability

The quick overview of the steps to set up and start managing strong authentication for your users is:

  1. Ensure that RiskMinder is installed and configured properly and that you have deployed the WAR files for the Administration Console.

    Note: See "Deploying RiskMinder on a Distributed 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 in a distributed environment.

  2. Log in to the Administration Console as MA (see "Accessing the Administration Console") and follow the steps in the Bootstrap wizard to initialize the system.

    Note: See "Bootstrapping the System" in the CA RiskMinder Installation and Deployment Guide for more information.

  3. Configure the Administration Console settings, which include UDS settings, global organization settings, Administration Console cache settings, and the basic username-password authentication policy for logging in to the Console.

    See "Configuring Administration Console Settings" for more information.

  4. Set up RiskMinder Server instances on different systems.

    See "Managing RiskMinder Server Instances" for more information.

  5. Configure the protocols that Administration Console, SDKs, and Web Services use to communicate to RiskMinder Server.

    See "Configuring Communication Protocols" for more information.

  6. Plan and create organizations. The organization architecture is flat and each organization that you create can map to a business unit in your enterprise.

    See "Creating and Activating Organizations" for more information.

  7. Plan and create the administrators (see "Creating Administrators") and custom roles (see "Working with Custom Roles"), if required.
  8. Create appropriate rules and rulesets to meet your business requirements, and assign these configurations.

    See "Managing Global Configurations" for more information.

  9. Create users in RiskMinder.

    See "Creating Users" for more information.

  10. If required, configure Secure Sockets Layer (SSL)-based communication between RiskMinder Server and its clients.

    See "Creating Trust Stores" for more information.

  11. If you are planning to extend the RiskMinder functionality by the use of callouts, then define and configure the required configurations.

    See "Configuring Callouts" 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").