Important! All the configurations and tasks discussed in this section can be performed by Global Administrators to apply the rules globally or by Organization Administrators to apply the rules for an organization.
See "Managing Organization-Specific CA Risk Authentication Configurations" for more information to access the task page for performing the organization-specific configurations:
A Callout is a custom component (which can be written in a programming language of your choice) to modify or augment the standard functionality of CA Risk Authentication. A Callout, typically, is an external process. As a result, it resides "outside" the CA Risk Authentication Server context and is hosted on a separate HTTPS-based server. Being an external process, you must configure a Callout by using the CA Advanced Authentication, so that it is invoked when required.
This section describes the types of Callouts that CA Risk Authentication supports and how to configure these Callouts to meet your business requirements. In addition, this section also walks you through the deployment, configuration, and use of the Sample Callout that is shipped in the CA Risk Authentication package:
Note: Ensure that the administrator performing configuration-related activities has the required privileges to perform these operations. For more information on the privileges available to administrators at each level, see "Summary of Administrative Privileges".
After you configure a Callout, the changes are not immediately active (available to your end users.) You must use the Migrate to Production link in the side-bar menu of CA Advanced Authentication to "move" all proposed configuration changes to your production database. See "Migrating to Production" for steps to migrate to production.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|