Performing Risk Evaluation on Gathered Information
Sample Application demonstrates how APIs are used to perform risk evaluation on the gathered data. To view the demonstration, perform the following steps:
aa821test
2327747
Sample Application demonstrates how APIs are used to perform risk evaluation on the gathered data. To view the demonstration, perform the following steps:
- Access the Sample Application URL in a browser window. This URL typically is:http://<app_server_host_name>:<port_number>/ca-riskauth-8.0-sample-application/index.jspIn the preceding URL, <app_server_host_name> represents the host name or IP address of the application server on which Sample Application has been deployed and <port_number> represents the port number at which Sample Application is available.The CA Risk Authentication Sample Application landing page appears.
- ClickEvaluate Riskto open the Risk Evaluation page.
- On the page, specify:
- The name of the user who is being evaluated for risk in theUser Namefield.
You can also specify the name of a user who is not yet enrolled with Sample Application, as discussed in "Performing Risk Evaluation".If you leave theUser Organizationfield empty, the value is automatically set to DEFAULTORG.(Optional) The name of theChannelwhere the transaction originated.(Optional) The correspondingNameandValuefields withAdditional Inputs, such as locale information and transaction amount for the current transaction. - ClickEvaluate Riskto generate the Risk Score and Risk Advice for the specified user.The Risk Evaluation Results page appears. If the user is not enrolled with CA Risk Authentication, then the advice is typically, ALERT. This advice changes when you create the user in CA Risk Authentication database, as discussed in "Creating Users" later in this appendix.
- ClickStore DeviceIDto store the specified type of Device ID information (Step 2) on the end user's device.
- ClickNext Stepto perform post evaluation for the specified user.The Post Evaluation page appears.As indicated on the page, if the advice on the previous page was INCREASEAUTH, then it is recommended that you plug-in your secondary authentication mechanism, so that the user performs another authentication before performing CA Risk Authentication post-evaluation steps.
- ClickPost Evaluateto generate and display the final Risk Advice for your application.The final result is displayed in the Post Evaluation Results frame of the page.