Migration guide for transitioning from the Client Legacy SDK to the AAFoundation SDK

Products

• CA Strong Authentication

Issue/Introduction

This document is a migration guide for transitioning from the Client Legacy SDK to the AAFoundation SDK in CA Advanced Authentication. ​ It is intended for developers and customers currently using the Legacy SDK. ​ 

Environment

CA Advanced Authentication

Resolution

The attached document guide provides step-by-step instructions, including code migration examples and configuration details, to ensure a smooth upgrade process. ​

Key Steps:

• Remove Legacy SDK Components: Delete specific header files and libraries associated with the Legacy SDK. ​
• Add AAFoundation SDK Components: Include new header files, frameworks (e.g., AAFoundation.xcframework, EncryptedCoreData.xcframework, SQLCipher.xcframework), and update project settings. ​
• Update Build Settings: Add paths for frameworks and headers. ​
• Remove Legacy Dependencies: Remove frameworks and libraries used by the Legacy SDK, such as SQLite. ​
• Code Changes:
• Update class names (e.g., OTP → Authenticator, AIDOTP_Account → AuthAccount). ​
• Modify function signatures for account provisioning and OTP generation. ​
• Implement delegate methods for handling provisioning, authentication, and account deletion. ​

• Add Database Files: Include AdvancedAuthDB.xcdatamodeld and CAAuthenticator.db in the application. ​
• Update Build Phase Settings: Add database files to the "Copy Bundle Resources" section. ​
• Build and Verify: Build the project and test account provisioning and OTP generation. ​

The guide emphasizes replacing Legacy SDK components with AA Foundation SDK equivalents, updating code, and ensuring proper configuration for successful migration. ​

Additional Information

For more information refer Consolidated iOS SDK for Mobile Authenticator documentation here.