CA Auth ID OTP Java Library Developer's Guide › Introduction

Introduction

Computers and mobile devices are now also used as a medium for home banking and performing financial transactions. Because these transactions involve sensitive user data, relying on just user name for authentication is not sufficient.

To secure the online transactions from Man-in-the-Middle (MITM) and other related attacks, CA Strong Authentication provides client applications that are based on CA CA Auth ID PKI and CA Auth ID OTP credentials. These software credentials provide two-factor authentication and are based on the patented Cryptographic Camouflage technique for securely storing keys.

There are client applications for computers and mobile devices.

To address your business requirements, you can extend and use the CA Auth ID OTP Client application. Alternatively, you can develop your own client application by using the Software Development Kit (SDK) that is shipped along with the client application.

This guide is intended to be a reference manual for you as you enhance the existing client application or create custom client applications for use with the CA Auth ID OTP for authentication on computers and mobile devices.

Note: The platform-independent version of the CA Auth ID OTP SDK is written in Java. This guide provides information about this platform-independent Java library (later referred to as "SDK" in this guide). For information about the CA Auth ID OTP SDK that is written in the Java, JavaScript, and Objective C programming languages for various mobile devices and computers, see the CA Auth ID OTP Authentication Developer’s Guide.

Important! Implementations of most client features provided in the SDK can be used with very little or no modification. However, only sample implementations of the Device Locking feature and the Storage feature are provided in the SDK. If you want to use these two features, you must use the SDK to develop your own implementations.

Important! This guide contains the terms Arcot, WebFort , RiskFort, WebFort, RiskMinder and AuthMinder in some of its code objects and other artifacts. The term ArcotID is now called as CA Auth ID . In addition, some of the topics in this guide do not follow the standard formatting guidelines.