CA Risk Authentication UNIX Installation Guide › CA Risk Authentication Configuration for SDKs and Web Services › Configure Device ID and DeviceDNA

Configure Device ID and DeviceDNA

CA Risk Authentication uses Device ID and DeviceDNA to register and identify the device that is used by a user during transactions. The Device ID is stored on the end user's device. The Device ID information is in encrypted format.

The following options are available for storing the Device ID on the end user's device. The plugin store is the most persistent storage option.

• Plugin store: The plugin store is a permanent store on the end user’s device. A Device ID that is placed in the plugin store cannot be deleted by common end-user actions such as clearing browser cache and deleting browser cookies. The plugin store is supported from CA Risk Authentication Client release 2.1 onward.
• Local storage that is provided in HTML5
• UserData store: This store is available only in Microsoft Internet Explorer
• Cookie store: Typically, on Microsoft Windows, the Device ID is stored in one of the following folders:
  • Internet Explorer on Microsoft Windows 7 or 2008:

    C:\Documents and Settings\<user_profile>\Application Data\Microsoft\Windows\Cookies\
    

  • Internet Explorer on Microsoft Windows 2003 or XP:

    C:\Documents and Settings\<user_profile>\Cookies\
    

  • Mozilla Firefox:

    C:\Documents and Settings\<user_profile>\Application Data\Mozilla\Firefox\Profiles\<random_dirname>\cookies.sqlite
    

  • Safari:

    C:\Documents and Settings\<user_name>\Application Data\Apple Computer\Safari\cookies.plist
    
    

Important! From CA Risk Authentication Client version 2.0 onward, the Device ID is not stored as a Flash cookie. If you have existing Flash cookies from an earlier release, then these cookies are automatically migrated to one of the stores that is listed earlier in this section.

File You Will Need for Device ID and DeviceDNA Collection

When you perform a complete installation or select to install CA Risk Authentication Evaluation SDK or Web Service in the Choose Install Set screen, the following file is automatically installed:

<install_location>\Arcot Systems\sdk\devicedna\riskminder-client.js

This file provides the functions to get and set the Device ID and DeviceDNA.

Enable Device ID and DeviceDNA Collection

To configure for a cookie to be set on the end-user computer, include riskminder-client.js in your application pages that get or set the cookies.

Follow these steps:

1. Copy the entire devicedna directory from <install_location>\Arcot Systems\sdk\ to the appropriate web application directory. Typically, the web application folder is at the following location:

   <APP_SERVER_HOME>\<Your_Application_Home>
   

2. Include the riskminder-client.js file in the required application pages. We assume that these files are located in a folder that is relative to the folder containing index.jsp.

   <script type="text/javascript" src="devicedna/riskminder-client.js"></script>
   

Migrate Flash Cookies from Preceding Releases

Flash cookies are not supported any more for storing the Device ID. However, if you have existing Flash cookies from an earlier release, then these cookies are automatically migrated to one of the supported stores on the end-user device when you complete the tasks described in Collecting Device ID and DeviceDNA in one of the following guides:

• CA Risk Authentication Java Developer’s Guide
• CA Risk Authentication Web Services Developer’s Guide