This chapter discusses the CA Auth ID OTP Software Development Kit (SDK) that you can use to build client applications for authenticating users by using their CA Auth ID OTP. The most common tasks performed using this SDK are provisioning the CA Auth ID OTP account to the user’s device and generating passcodes. Other tasks that you can perform using the SDK include resetting CA Auth ID OTP PIN, fetching and deleting the accounts from default location, storing accounts in a custom location, locking account to the device by using device parameters of your choice, and checking library version.
The chapter first introduces you to the interfaces and classes that you will be using for different tasks mentioned in the preceding paragraph, and later explains the usage in detail.
To perform CA Auth ID OTP authentication, you need to first create an account for the user that contains the CA Auth ID OTP information and save it on their device. The Provisioning CA Auth ID OTP Accounts section discusses the provisionRequest() method in the OTP class that you need to use to create CA Auth ID OTP accounts.
After an account has been provisioned, it must be stored on the user’s device. The Choosing Custom Storage Medium section provides information about storing accounts. The Storing Accounts in Memory section describes a sample implementation for using memory as the storage location.
To perform CA Auth ID OTP authentication, the users have to first generate passcode, which is required during authentication. The Generating Passcodes section discusses the generateOTP() method in OTP class that you need to use to generate passcodes.
The Resetting CA Auth ID OTP PIN section discusses the resetPin method in the OTP class that you can use to change the user’s CA Auth ID OTP PIN.
The Managing Accounts section discusses the methods of OTP class that you need to use for reading and deleting CA Auth ID OTP accounts stored in the default location.
Depending on the device that is being used, CA Auth ID OTP library supports default parameters for locking the account to the device. If you want to lock an account to the device by using the device parameters of your choice, then implement the DeviceLock interface, as discussed in the Device Locking section.
The Reading CA Auth ID OTP Account Details section discusses the OTP class fields that hold the CA Auth ID OTP details such as, unique identifier for the account, timestamp when the account was used, number of times the account was used, and friendly name for the account. It also discusses the classes that are used to set and get additional CA Auth ID OTP attributes.
The Synchronizing the Client and Server section discusses how to use the syncRequest() method to construct and send a synchronization request to the server.
The Checking Library Version section discusses the getVersion() method in the OTP class for checking the version of the CA Auth ID OTP SDK.
The Converting the CA Auth ID OTP section discusses the provisionRequest() method and callback() method for converting the CA Auth ID OTP into a string and back into an account object.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|