Community - I want to highlight a recent discussion. As Paul writes: "fineract must support self-service". (see emails https://lists.apache.org/thread/qfydfzclwb2wstgqwcgq5hgv7lvm11dr )
I agree. However, as previously discussed, the (now removed) implemented functionality "self service in Fineract" created security issues and was unsuitable for a production environment. We have broadly requested a group to step forward and assist. With no progress on that, vendors are building their own "plug in". That is a natural consequence, although I would prefer to see those contributions at Fineract. I have created a GSOC ticket, https://issues.apache.org/jira/browse/FINERACT-2439, to begin addressing this deficit in the Fineract software. The proposal is essentially the same as it was two years ago - to create a separate component that sits between the existing Fineract system and the end-users (on apps, on websites). This GSOC project is intended to move us forward. How important is this functionality? Very. Where should it sit given our current architecture? On the fineract project in a new repo (different component) and it should use its own authentication flow. What should users or deployment teams do today to address this gap? You can build your own or use a vendor solution. If you build your own you can leverage the data model and API patterns found in the git history. (just go back to a commit circa early 2025) We cannot recommend deploying an archived release. What should this look like in the long term? To be determined by those working on it. It is possible that we adjust the data model of Fineract to accomodate this properly. I hope that helps. James
