FAQ
1. What is the CAF SmartAuth SDK and what is its main functionality?
Answer:
The CAF SmartAuth SDK provides a customizable solution for user authentication through various methods, including live facial verification, SMS, and email. It’s ideal for enhancing security in applications requiring user authentication, particularly for scenarios like user onboarding, secure access, and identity verification.
2. What are the system requirements for the CAF SmartAuth SDK on iOS?
Answer:
The SDK is compatible with iOS 13.0 and above, supporting a wide range of modern iOS devices. Ensure your project meets the minimum iOS target of 13.0.
For further requirements, including specific Xcode and Swift versions, refer to the Requirements section.
3. What permissions are required to use the SDK?
Answer:
The SDK requires the following permissions:
Camera access (
NSCameraUsageDescription
) for facial verification.Localization access(
NSLocationWhenInUseUsageDescription
) for localization context.
Ensure these permissions are properly declared in your app's Info.plist
file and handle runtime permission requests if necessary.
4. How do I integrate the CAF SmartAuth SDK into my iOS project?
Answer:
To integrate the SDK:
Add the SDK framework to your Xcode project.
Configure the necessary permissions for camera and internet access in your app’s
Info.plist
.Initialize the SDK in your application's lifecycle, typically within
viewDidLoad()
of your main view controller.
Refer to the Source Code for step-by-step integration details.
5. What is the current version of the SDK, and where can I find version-specific details?
Answer:
The SDK version is periodically updated. For the latest version information, release notes, and changelogs, check here.
6. How do I start the authentication process using the SDK?
Answer:
To initiate the authentication process:
Configure a SmartAuth session with the desired authentication policies (e.g., face verification, SMS, email).
Start the session using the SDK’s builder.
Capture and handle the results in the delegate callbacks.
For more details, see the Authentication Setup section.
Last updated