The Mifos Initiative recognizes how critical the self-service capabilities are to the users of Fineract and Mifos and do require a more secure way of connecting to and administering trusted first and third party customer facing applications. Mifos and members of the community are working on the design and implementation of this plugin which will be maintained as a separate open source Mifos plug-in on top of Fineract and welcome any feedback or input into its design.
Thanks, Ed On Thu, Mar 13, 2025 at 10:08 PM Paul <pchristi...@gmail.com> wrote: > I'm not technical enough to speak about the tech portion, but from a > business perspective / opinion, Fineract MUST support self service in their > db schema or become intentionally obsolete. Fineract does not need to > support the connector or gateway. They already exist in multiple flavors. > > The fundamental regulatory and ethical principles of *Open Banking* emphasize > consumer control, which necessitates a self-service function. The two can > not be separated . . . As of today, 81 countries have already implemented > an open data / open banking policy (required by law) with ~17 more > implementing / phasing in policies over the next year, (US being one of > them). That's 98 countries of 192 chartered in the UN . . . . have already > codified consumer rights to the data and others are following. > > Regardless of the structure of the connector, node or gateway method which > certainly could (and maybe should) be outside the core product, at the end > of the day, those gateways must still connect to the Fineract backend and > the supporting data points should NOT be custom in my business opinion. > > Regards, Paul > > > On Thu, Mar 13, 2025 at 8:31 AM Felix van Hove <fvanh...@gmx.de.invalid> > wrote: > >> Hi all, >> >> Do you intend to withdraw the capability to *manage* self service users >> and potentially certain features of the Self Service app by non-end >> users (which is hinted at by menu items in the Mifos X client) too? >> >> On Wed, 31 Jan 2024, 21:45 VICTOR MANUEL ROMERO RODRIGUEZ, < >> victor.rom...@fintecheando.mx> wrote: >> > As an alternative you can use solutions for accessing the APIs like API >> > Gateways and Access Management. >> >> Is there any guideline or anything that explains e.g. to a smallish >> microcredit org how to set something like this up in the future? I >> assume you don't want to put the user management into the API gateway too. >> >> Felix >> >> On 12/03/2025 20:07, James Dailey wrote: >> > Yes please. It would make sense now to remove it - it will still be >> > "there" in the code if someone really wants to figure it out but having >> it >> > gone would reduce some surface area of application concerns. Also >> > vendors have had enough notice on this to have come up with their own >> > approach. >> > >> > Expanding this... >> > I also think Fineract should probably build its own "reference version" >> for >> > the same functionality but in a different github at Apache Fineract. >> This >> > would fit better into an overall architecture, where you have the >> component >> > using secure methods to connect to the backend APIs and then exposing >> > different customer facing APIs . The auth is different for such a >> > component, as it relies on identity models for the end user, which are >> > fundamentally different than identity validation for employees of a >> bank, >> > credit union, etc >> > >> > >> > >> > James Dailey >> > >> > >> > >> > On Wed, Mar 12, 2025 at 8:50 AM Ádám Sághy <adamsa...@gmail.com> wrote: >> > >> >> Hi guys, >> >> >> >> I would like to pick up once again this topic: Self-service in >> Fineract. >> >> >> >> Since we just had a release and this functionality was still not >> removed, >> >> i was wondering whether we want to do it now and by the time of the >> next >> >> release we dont need to worry about that anymore. >> >> >> >> This was already a topic a couple times whether the existence of this >> >> functionality in Fineract is good or bad, but If I recall correctly, >> it was >> >> majorly considered as a bad thing (problematic from security point of >> view >> >> as well). >> >> >> >> Should we have a casual or official vote regarding the self-service >> >> functionality? >> >> >> >> Regards, >> >> Adam >> >> >> >> On 2023. Nov 15., at 14:34, mumin iddrisu <mismis...@gmail.com> wrote: >> >> >> >> Hello James >> >> Thank you for the feedback. >> >> I will be looking out for the solution in the coming months. >> >> >> >> Regards >> >> Abdul >> >> ---mis >> >> >> >> >> >> On Wed, Nov 15, 2023 at 4:01 AM James Dailey <jdai...@apache.org> >> wrote: >> >> >> >>> Abdul - >> >>> >> >>> We encourage everyone to move away from the self-service component. >> We >> >>> are going to be revising this shortly as it is not designed for a >> >>> production environment. >> >>> In lieu of this we will propose a solution. This is probably a month >> or >> >>> more away. >> >>> >> >>> The history is that we've identified issues with this component and >> have >> >>> slated it, in many roadmap decisions, for immediate removal. It is >> getting >> >>> close to that point now; we do need to find a way to describe what to >> do >> >>> without the Self Service component. >> >>> >> >>> Jdailey >> >>> VP Apache Fineract >> >>> >> >>> On Tue, Nov 14, 2023 at 8:43 AM mumin iddrisu <mismis...@gmail.com> >> >>> wrote: >> >>> >> >>>> Hello Team >> >>>> Has anyone successfully deployed the self-service feature? >> >>>> If yes please let me know which build you are using. >> >>>> >> >>>> Regards >> >>>> Abdul >> >>>> ---mis >> >>>> ᐧ >> >>>> >> >>> >> >> >> > >> >> > > -- > -- > Paul > -- *Ed Cable* President/CEO, Mifos Initiative edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 *Collectively Creating a World of 3 Billion Maries | *http://mifos.org <http://facebook.com/mifos> <http://www.twitter.com/mifos>
