Error Scenarios

In case the end user cannot complete challenge (step 5 in Authentication workflow) on the first try, VIDA Authentication server responds (step 7 in Authentication workflow) with a new, updated challenge along with a new bearer token that shall be used to perform provisioning/authentication and submit challenge response (step 5 in Authentication workflow) again. This will enable the client to resume authentication in case of an inadvertent failure

Error Codes

HTTP Code	Error Msg	Error Description
400	invalid_request	message=Invalid client id
400	invalid_request	message=Missing client id
400	invalid_request	message=Invalid or expired bearer token
401	unauthorized_client	message=Unauthorized client
401	access_denied	message=Bad request. Missing or invalid parameter: type
401	access_denied	message=Bad request. Missing or invalid parameter: template_url
401	access_denied	message=Bad request. Missing or invalid parameter: image
401	access_denied	code=1039;message=connection pool shutdown
401	Selfie photo does not match with reference photo	code=1040;message=Selfie photo does not match with reference photo;livelinessScore=0.103826;faceMatchScore=0.396705
401	access_denied	code=21004;message=Unprocessable Entity
401	access_denied	code=1051;message=Face Occluded
401	access_denied	code=1055;message=No face detected
401	access_denied	code=1056;message=JPEG decoding error
401	access_denied	code=1006;message=invalid id
401	access_denied	code=1602;message=Transaction Not Found
401	access_denied	code=1603;message=Could not fetch the scores for given transaction
401	access_denied	code=1604;message=Image not found for given transaction
404	Realm does not exist