nabilfeghali's account

we have uploaded OneSpanIdVerificationREST.txt containg json requests and responses

Hi Will, 

We still have the same error even if we clear all browser data (delete all cookies and all stored data) once we copy the URL in a browser tab we get the page not found
https://salesdemo-dealflo.uat.eu1.tid.onespan.cloud/sales/#/esign/0f42d17d-d215-468c-a047-662b85816807?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiIsImtpZCI6IjI4NTliZDQwLTAyOTAtNGE3ZC1hOWZhLWQ5YjMxYmRiMGZiYyJ9.eyJyb2xlIjoiQ3VzdG9tZXIiLCJzY29wZSI6WyJzZXNzaW9uX2NyZWF0aW9uX2F1dGhvcml6YXRpb25fY29kZSJdLCJ0cmFuc2FjdGlvbl91dWlkIjoiMGY0MmQxN2QtZDIxNS00NjhjLWEwNDctNjYyYjg1ODE2ODA3IiwiY2xpZW50X2lkIjoiUGF0aF9Tb2x1dGlvbnMiLCJqdGkiOiIzNDllZWNlNy1mNzlkLTRmMTktOGU5My01OTM2ZDQ4NjFhNTIiLCJpYXQiOjE2MzEwMjE1MDgsImV4cCI6MTYzMjMxNzUwOH0.JOhd23N_mtP695rdeqAeUs76TbjV7k0ZmZLDFvN5neJiuPd2t9vqixt6XJyKxkIU2A00X8etGIl552ocwmqDsw

then if we debug the network tab we notice that there is a 401 at the level of https://salesdemo-dealflo.uat.eu1.tid.onespan.cloud/api/transaction/0f42d17d-d215-468c-a047-662b85816807/session/ with following response {"error":"invalid_token","error_description":"Client with id Path_Solutions not supported"} returned .

we are wondering why the token is invalid noting that we have passed the same token value returned from the create transaction response. 

thank you

Thank you Will, It's working now

Dear Will,

Could we have a customized workflow based on our business requirement ? like for example a customized workflow in which we will apply the Document OCR Parsing where we will take only an image capture of the national id document and benefits from the OCR data/fields automatically extracted from the doc (attached onespan_document_captue.jpg) in addition to the checking on the validity of the scanned doc. And to have another customized workflow for the liveness detection where the user will take a selfie capture with smile and then we can benefits from the liveness detection service separately ? (attached onespan_face_capture_and_smile.jpg)

This way, and in case feasible, we can benefits from the Document Verification and OCR Parsing from our backend services without the need of the customer intervention to take a live selfie, so we can validate a set of documents uploaded by the customer in backend without the customer intervention, by calling OneSpan IDV REST API in which we can provide the byte arrays (or base 64) representation of the Document Capture and receive in response the OCR fields and Document Scoring results.

Plus could we have please some details on the above workflows, for example what is the difference between "00000000-0000-0000-0000-300000000007" and "00000000-0000-0000-0000-310000000007" ? because we have tried to create transactions with each one of them and we found that both of them are asking for Document Capture and for Face and Smile Capture, (step  onespan_document_captue.jpg then step of onespan_face_capture_and_smile.jpg ), what's the difference between them ?

Thank you,

Nabil,

Attaching the above mentioned screen shots : onespan_face_capture_and_smile.jpg and onespan_document_captue.jpg