Diagnosing Encryption/Decryption Behavior
Learn how to diagnose and resolve Encryption/Decryption Behaviors.
Diagnosing a "Decryption not Possible" Error
The majority of "Decryption not Possible" Errors are due to one of the following reasons:
- Public and Private Encryption Keys do not match.
- An incorrect Device/Server Key was provided to FaceTec.
- Liveness Checks, 3D FaceScans, or ID Scans are incorrectly being encoded in base64.
Important Note: The Server's HTTPS APIs require base64 encoding for all biometric and image data sent.
Before proceeding, it is imperative to determine that both your Public & Private FaceScan/FaceMap Encryption Keys and Device/Server Keys are correct.
- First, verify that your Device and Server Keys are correct by confirming they match the ones in your FaceTec Dev Account.
- Please Note: Copy/paste errors that change even one character in the key will cause Encryption/Decryption problems, so make sure to double-check these values!
- Afterward, inspect your Public Encryption Key and confirm it was Generated from the Private Encryption Key on your Server.
- Please Note: Copy/paste errors that change even one character in the key will cause Encryption/Decryption problems, so make sure to double-check these values!
- Be Cautious: A frequent pitfall we have observed is that the Public Key was updated by the Device-side Developer, but the Private Key was not updated by the Server-side Developer, or vice versa. The Public/Private Key Pair MUST match, or it will cause an Encryption/Decryption exception.
If you have confirmed that both your Public & Private FaceScan/FaceMap Encryption Keys and Device/Server Keys are correct, then the behavior may be a result of incorrectly encoding in base64. To verify this, please check how you are encoding your Liveness Checks, 3D FaceScans, IDScans, and Audit Trail Images.
Requesting Assistance
If you have verified that none of the three reasons are the cause of your "Decryption not Possible" Error, then please ZIP both your Device SDKs and FaceTec Server and send them to FaceTec via a Support Request.
Decryption/Key Behaviors when Using the Testing API
When the Device SDK is running in development mode, the 3D FaceScan/Map Encryption Public Key in the configuration file is ignored. The Test API Public Key is used instead.