Previous Topic: SDK ErrorsNext Topic: Uninstall CA Risk Authentication Server


How to Uninstall CA Risk Authentication

You can uninstall CA Risk Authentication from the Windows Control Panel or run the uninstaller file (Uninstall CA Risk Authentication.exe) to remove CA Risk Authentication from your system.

After you complete the uninstallation process, perform the post-uninstallation tasks to clean up the residual WAR files and entries.

Important! Before you uninstall CA Risk Authentication, first remove its the schema first and then proceed with the uninstallation process.

If you installed both CA Strong Authentication with CA Risk Authentication and you are uninstalling only CA Risk Authentication, follow the guidelines given in the following sections. These guidelines ensure that you do not remove or modify the common components that are also used by CA Strong Authentication.

This section guides you through the steps for uninstalling CA Risk Authentication and its components.

  1. Drop CA Risk Authentication Schema
  2. Uninstall CA Risk Authentication Server
  3. Perform Post-Uninstallation Tasks

Drop the CA Risk Authentication Schema

If you plan to uninstall only CA Risk Authentication then, do one of the following steps:

Note: If you plan to uninstall both products, then you can drop both schemas in any order.

Follow these steps::

  1. Navigate to the following directory:
    <install_location>\Arcot Systems\dbscripts\
    
  2. Based on the database type that you use, navigate to one of the following subdirectories:
  3. Run the scripts in the following order to drop all database tables of CA Risk Authentication and related components:
    1. Run drop-riskauth-8.0.sql.
    2. If applicable, run drop-riskauth-3dsecure-8.0.sql.
    3. If you have not installed, run drop-arcot-common-8.0.sql.

      Note: The drop-arcot-common-8.0.sql script is used to remove the schema for common components. This schema is used by both CA Strong Authentication and CA Risk Authentication. If you have already (successfully) installed CA Strong Authentication, you must not drop this schema because CA Strong Authentication can continue to use it.

  4. If you have no further use for the database user account that you had created for the CA Risk Authentication schema, delete that user account.