GitLab

Implement another GlassInputRequest (I would call it Glass authorizationRequest) where the user is prompted to accept/deny the Glass authorized request it received, and it should contain detailed information about what the user is authorizing

This will require an GlassAuthorization data structure to be able to hold all the required paths to the data (if we requesting the id for instance, this path should be something like egov..I'd, the the name on the cc it should be egov..id.name). The naming is related to the query syntax and will be addresses on a separate issue)

Example: Evidence request from third party:

• wallet receives Glass authorized request containing the Glass evidence request.
• wallet displays screen containing for each evidence requested:
• the specific documents/data requested (eventually the conditions)

This screen already exists in the UI mocks