Known issue: Wallet Backend as proxy for the cross-origin http requests

[kkmanos]

Since wwWallet now runs on the browser after the PR which transferred the protocols to the frontend, the issue with cross-origin request blocking was raised when communicating with external servers for the issuance and presentation flows.

A temporary solution that has been adopted is the utilization of the wallet-backend-server as the proxy for the http requests directed to the Issuers and Verifiers.

However, the primary target of the wwWallet project is always to build an architecture which prevents the wallet-backend-server from gaining insight to personal or transaction-related data being exchanged between the wallet-frontend and external parties (issuers/verifiers). That being said, the HTTP proxy module needs to be eliminated and figure a different way to tackle this challenge which will maintain the anonymity of the wallet-frontend.

Possible solution

In the case where the wwWallet is wrapped with a native wrapper, then the native wrapper application can be utilized to intercept the HTTP calls and execute them on behalf of the browser app to avoid cross-origin request blocking.