Session Tokens
Session Tokens provide additional tamper-proofing and reduce the surface area of potential attacks.
Technical Description
The FaceTec Server generates an encrypted, signed piece of data called a Session Token, which is used as an input in the device-side User Session launch code. The Session Token is then embedded into the 3D FaceScan and subsequently verified as a part of processing the FaceScan back on the server. This allows enhanced verification of the validity and integrity of 3D FaceScans as well as the ability to configure 3D FaceScans to expire. The Session Token Expiration Time is 30 minutes and prevents the 3D FaceScan from being used 30 minutes after creation.
Session Tokens are required for core FaceTec APIs like 3D Liveness and 3D:3D Matching to succeed. The result of the Session Token evaluation from the FaceTec Server is returned on the faceScanSecurityChecks.sessionTokenCheckSucceeded flag. The sessionTokenCheckSucceeded flag must be true for overall success to be true.
Integrating Session Tokens
The Sample App and the Postman Test Suite demonstrate how Session Tokens are retrieved from the server and used in the platform-specific User Session launch code. Session Tokens must be integrated as shown in the Samples for successful 3D Liveness and 3D:3D Matching.