Hi Wilfred, Thanks for the detailed update. The sandbox instance is still running on the 18.03 release version of both Fineract and the front-end. and Fineract 1.5 is compatible with the Mifos release version 21.07 or the latest Develop branch.
Backward Compatibility sounds good technically but will be challenging on the functional/feature side and also at branch maintenance. For example: Fineract might have new features developed, but backward Compatible Mifos may not have the screens to use that and vise-verse. Mifos /Fineract follows the approach of adding fixes/features on the develop branch always and does the tag cut-off during the release process. Hence I feel we should always go with the latest of both code bases or the correct release version codebases to get the full benefit of the features/changes made. Latest releases Fineract: 1.5 https://github.com/apache/fineract/releases/tag/1.5.0 Community App: https://github.com/openMF/community-app/releases/tag/MIFOSX-21.07.01.RELEASE Having said my opinion, I will leave it open to the community around this discussion, we could always go with what is best for the users. Regards, Bharath Lead Implementation Analyst | Mifos Initiative Skype: live:cbharath4| Mobile: +91.7019635592 http://mifos.org <http://facebook.com/mifos> <http://www.twitter.com/mifos> On Mon, Oct 25, 2021 at 11:14 PM Wilfred Kigenyi <wkige...@gmail.com> wrote: > Thanks Alot for your response Bharath, > > I later discovered that there is a difference between the authentication > api of mifos and that of fineract 1.5 and that is where the issue was > arising from. Mifos requires a POST request to > 'authentication?username={username}&password={password}' whereas fineract > requires a POST request to 'authentication' with a body > {username,password}. I had originally written my request based on fineract > so it was failing on the mifos instance. > > Should be an issue though, should there be backwards compatibility between > fineract and mifos. My thinking was that both request formats should be > accepted since the api version is still the same i.e. v1. > > Otherwise, because of the responses I have received from you and the other > community members I feel welcome and eager to contribute to this cause. I > will share the URL at a later time when done with some TODOs. > > Thanks. > Regards. > Wilfred > > On Mon, Oct 25, 2021 at 4:26 PM Bharath Gowda <bgo...@mifos.org> wrote: > >> Hi Wilfred, >> >> Great to hear about the new UI development from your End. We would be >> happy to help you, please do not hesitate to share any questions you have >> to our Develop and User mailing list which I have cc'd in this thread. >> >> >> Could you please share the URL which you are using to connect your local >> UI to https://wkigenyi.sandbox.mifos.io/#/ server? >> >> If you are running your UI through grunt serve then the following URL >> should work >> >> http://localhost:9002/?baseApiUrl=https://wkigenyi.sandbox.mifos.io&tenantIdentifier=default >> >> Check the UI Port as per your configuration. >> >> Regards, >> Bharath >> Lead Implementation Analyst | Mifos Initiative >> Skype: live:cbharath4| Mobile: +91.7019635592 >> http://mifos.org <http://facebook.com/mifos> >> <http://www.twitter.com/mifos> >> >> >> On Sun, Oct 24, 2021 at 2:18 PM Wilfred Kigenyi <wkige...@gmail.com> >> wrote: >> >>> Greetings Bharath, >>> >>> I am developing a customer facing app based on Fineract 1.X >>> An instance was created for me and I want to test it. >>> https://wkigenyi.sandbox.mifos.io/#/ >>> >>> However when I try connecting to this instance using my custom UI I get >>> a 401 response on attempting to login. >>> I am logging in with mifos/password and my headers are below:[image: >>> Headers.PNG] >>> What do I need to change to make my UI work with the instance? >>> >>> Thanks and Regards >>> Wilfred >>> >>> >>>
_______________________________________________ Mifos-users mailing list Mifos-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-users
