Implement support for reading ICAO-documents in the native apps

[leifj]

This issue pertains to both iOS and android native apps

Epic

In order to support issuing our own personal identity documents (aka PIDs) the native apps need the ability to read, validate and extract information from ICAO documents.

Background

ICAO documents (passports mostly) are goverment issued identity documents that contain authenticated biometric information in the form of JPEG2000-pictures that can be used to perform a form of remote user identity proofing using modern NFC-capable mobile phones. The process typically involves the following steps:

1. User is asked to take a photo of the MRZ-code on the bottom of the passport main page or back of the ICAO card
2. The MRZ-code picture is turned into text string(s) using OCR
3. User is asked to place the passport behind the phone where the NFC reader is located
4. The MRZ code is used to authenticate to the ICAO-document
5. The JPEG2000 picture is read from the ICAO document
6. User is asked to take either a picture, a series of pictures or a short video to create data for comparison with the picture in the passport
7. Liveness check are performed to ensure that the user is actually present
8. The picture and liveness-checked picture/video is compared

Typically services that provide these functions include SDKs that make this process simple to implement in a native app.

[tladesignz]

Ok, I extensively dove into our current favourite vendor's SDK documentation.
It's actually pretty straightforward to implement and seems reliable and easy for the user, at least as much as a passport scan can be. The NFC passports definitely help with increasing the ease and reliability.

Next steps

• The implementation will need to have a server side part on our side, too, which proxies the requests and adds a database identifier from our side. (Not sure, if, in our case, that should actually come from the frontend, anyway.)
• The wwWallet JS frontend will need UI to initiate such a scan.
• Hence the JS frontend will need a test, if it runs in a wrapper to decide if that option should be shown.
• It will need to receive the scanned passport data and create a credential from that.
• The scanned passport data would be either fetched in our server's backend when passing through the response from the provider's server, where it will create a credential and trigger the JS frontend to load that.
• Or, if the proxy endpoint on our server should be kept small, we will need to pass the passport data from the wrapper to the JS frontend.
• To keep the amount of shared code high, passport data processing should be implemented in the JS frontend, in which case the API would be pretty straightforward and basically defined by the vendor's response data structure.
• If that is not feasible, there would need to be an API defined on the JS side, which the wrappers need to fulfill.

@leifj, waiting on more instructions on how to proceed.