This document describes in detail the different authentication factors available via Pinn. Our API/SDKs allow for you to select which factors to enforce in any given scenario.
||All authentications enforce this method by default, this method uses special private keys in your app to produce a signature that can only be generated on a specific end user's mobile device while your app is running||Local|
||This method verifies a users presented left palm biometric data against the enrolled template||Remote|
||Verifies either a user's left or right palm against the enrolled biometric template, whichever palm the end user presents. This gives the end user flexibility to provide whichever palm is more convenient to them.||Remote|
||Verify the user with an on-device biometric available to their phone, commonly this is a fingerprint, face or iris scan.||Local|
||This auth method prompts the end user for their on-device passcode.||Local|
Using specialized cryptographic keys, both local_biometric and local_passcode enable your backend to remotely prove the end user performed these authentication methods successfully. Your local biometric data or passcode never leave the end-user's device, instead a cryptographic signature provides evidence that the authentication was completed on a given device/app.
Move onto our next section within key concepts regarding ID Tokens.
We are here to help! Contact us with any development related questions at email@example.com and we'll reach back in a timely manner.