Thank you Victor. +1 on the contribution of the proxy. I look forward to seeing the Pull Requests in the appropriate places. Do you have some high level flows for documentation of this approach to put on the wikis?
For everyone's benefit, BIAN is the Banking Infrastructure Architecture Network and is a non-profit that is aligning service oriented architectures across all banking domains. https://static.bian.org/wp-content/uploads/2015/07/BIAN_landscape4.0.pdf Thanks, - James On Tue, May 21, 2019 at 2:19 PM VIctor Romero <[email protected]> wrote: > Hi, > > We have been working in a proxy using node.js and has been deployed to > firebase, but any capable node.js server could be used. > > Mobile wallet <-> proxy <-> Mifo's/Fineract APIs > > We have used the proxy to accomplish the goals to be aligned to BIAN 4.0 > and OpenBanking Mexico usability guidelines. > > We already have donated the code to Mifos and we are removing the legacy > code. And the proxy code can be also donated. > > Regards > > Victor > > > > Obtener BlueMail para Android <http://www.bluemail.me/r?b=14874> > En 21 may 2019, en 2:54 p. m., James Dailey <[email protected]> > escribió: >> >> Devs - I would like to resurface this discussion. Please see my original >> post above and Juhan's specific thinking. >> >> (direct) Channel access without a middle-layer or proxy of some kind is >> not recommended in production. >> >> By implication, anyone building a front end app that is aimed at end >> users and all of those already built, should be labeled on our sites as >> "for demo purposes only". >> From what we know all of the (larger) companies out there that are using >> a customer facing front end, they are securing it beyond what is provided >> by default on our community built apps. >> >> And, we should have a group working on the design of that proxy/middle >> layer for both Fineract1.x and FineractCN. >> >> @ShivanshTiwari please note for Mifos Mobile Wallet project. If there >> is a way to include a proxy service that speaks to your app and then to the >> backend APIs that would be a good idea I think. >> >> - James >> @jdailey67 >> >>
