[jira] [Commented] (FINERACT-2120) Add functionality for withdrawals to a linked account and disbursements to a linked account
[ https://issues.apache.org/jira/browse/FINERACT-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879348#comment-17879348 ] James Dailey commented on FINERACT-2120: This is not sufficiently detailed as a ticket for someone to evaluate. And, then the pull requests were done without discussion on list or any comment here. While we have a lazy consensus approach, without specificity there can be no consensus. Please restart this process with email and details... get consensus. Then do a pull request. > Add functionality for withdrawals to a linked account and disbursements to a > linked account > --- > > Key: FINERACT-2120 > URL: https://issues.apache.org/jira/browse/FINERACT-2120 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Apurb Rajdhan >Priority: Major > > Add features like withdrawal to linked account and disburse to linked account > to increase interoperability between FSPs using Payment Hub APIs and Interop > table. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2077) Release 1.10 macro ticket
[ https://issues.apache.org/jira/browse/FINERACT-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2077: --- Fix Version/s: 1.10.0 (was: 1.11.0) > Release 1.10 macro ticket > -- > > Key: FINERACT-2077 > URL: https://issues.apache.org/jira/browse/FINERACT-2077 > Project: Apache Fineract > Issue Type: Improvement >Reporter: James Dailey >Assignee: James Dailey >Priority: Major > Fix For: 1.10.0 > > > This is the ticket for the release 1.10. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1803) Extension point: content repository
[ https://issues.apache.org/jira/browse/FINERACT-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1803: --- Fix Version/s: (was: 1.10.0) > Extension point: content repository > --- > > Key: FINERACT-1803 > URL: https://issues.apache.org/jira/browse/FINERACT-1803 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > This is a low hanging fruit. Currently the content repository is set via a > database configuration table. It would be better and more consistent to move > this to application.properties instead. Dependency injection best practices > are not followed, so we would improve that too and have - as a nice side > effect - less files to deal with, no more database dependency and users could > develop more custom content repositories. > While we are at it: remove the unnecessary distinction between "files" and > "images"... and within images: no need to distinguish between client, staff > or any other image for that matter. > Provide a migration tool to import existing legacy files/images into the new > repository format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2068) Loan account status history
[
https://issues.apache.org/jira/browse/FINERACT-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-2068:
---
Fix Version/s: (was: 1.10.0)
> Loan account status history
> ---
>
> Key: FINERACT-2068
> URL: https://issues.apache.org/jira/browse/FINERACT-2068
> Project: Apache Fineract
> Issue Type: New Feature
>Reporter: Mihaly Dallos
>Priority: Major
> Labels: PepperSoup
> Fix For: 1.11.0
>
>
> In order to better keep track of loan lifecycle changes and be able to emit
> external events, loan lifecycles changes should be stored and configured for
> watcher.
> We need to add an extra listener for the
> {{{}LoanStatusChangedBusinessEvent{}}}. When this event was triggered, we
> need to fetch the actual business date and store in the database.
> These details can be helpful to create business steps and reports which rely
> on these details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-2062) Use 48 weeks in a year when interest rate is per month
[ https://issues.apache.org/jira/browse/FINERACT-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2062: --- Fix Version/s: (was: 1.10.0) > Use 48 weeks in a year when interest rate is per month > -- > > Key: FINERACT-2062 > URL: https://issues.apache.org/jira/browse/FINERACT-2062 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.9.0 >Reporter: Kigenyi Wilfred >Priority: Minor > Fix For: 1.11.0 > > > Given that the interest rate period on a loan is monthly and client has > chosen to make weekly repayments, it makes more sense to assume that there > are 4 weeks in the month and 12 months in the year which comes to 48 weeks > rather than assuming the traditional 52 weeks in the year. > For example if a loan has a flat interest rate of 2% Per month and the > principal is 1000 and the repayments are weekly, weekly interest is currently > computed as follows: > interest per week = (0.02*12*1000)/52 = 4.61538 > it would make more sense if interest per month is computed as follows: > interest per week = (0.02*12*1000)/48 = 5 > > In other words there is no need for computing weeks in a year when we are > dealing with a month. There are 4 weeks in a month and this assumption > calculates a more reasonable figure as compared to when we compute weeks in > year. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1986) Modular Security Architecture: Phase 3
[ https://issues.apache.org/jira/browse/FINERACT-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1986: --- Fix Version/s: (was: 1.10.0) > Modular Security Architecture: Phase 3 > -- > > Key: FINERACT-1986 > URL: https://issues.apache.org/jira/browse/FINERACT-1986 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > Refactor current authorization (aka "permission enforcement") as a module; > some refactorings needed in REST resource classes b/c current enforcement not > following best practices; 100% backwards compatible, authorization as before, > same database tables. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1989) Add Spring Modulith
[ https://issues.apache.org/jira/browse/FINERACT-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1989: --- Fix Version/s: (was: 1.10.0) > Add Spring Modulith > --- > > Key: FINERACT-1989 > URL: https://issues.apache.org/jira/browse/FINERACT-1989 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > Automatic dependency diagram generation via Spring Modulith. Add module > documentation stubs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1951) Add filter on cashier teller management for transactions
[ https://issues.apache.org/jira/browse/FINERACT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1951: --- Fix Version/s: (was: 1.10.0) > Add filter on cashier teller management for transactions > > > Key: FINERACT-1951 > URL: https://issues.apache.org/jira/browse/FINERACT-1951 > Project: Apache Fineract > Issue Type: Improvement > Environment: Mifos community App 21.07.3 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2023-07-09-18-24-49-473.png, > image-2023-07-09-18-26-53-403.png > > > In the cashier teller management module, the cashier may need to filter and > reconcile balances on a daily basis side the cashier teller module. For this > to be achieved, there need to be filters that allow the user to d so as per > the screenshot below > !image-2023-07-09-18-26-53-403.png|width=587,height=405! > > Filter for; > * Transaction type either cash in or cashout > * Transaction date > * Transaction ID > We also need to change the layout to have the last transaction on the first > page. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1095) Remove direct sqlSearch support from /clients and all other APIs [Security & Performance]
[
https://issues.apache.org/jira/browse/FINERACT-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1095:
---
Fix Version/s: (was: 1.10.0)
> Remove direct sqlSearch support from /clients and all other APIs [Security &
> Performance]
> -
>
> Key: FINERACT-1095
> URL: https://issues.apache.org/jira/browse/FINERACT-1095
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Michael Vorburger
>Assignee: Mihaly Dallos
>Priority: Major
> Fix For: 1.11.0
>
>
> While code reviewing PRs from [~Manthan] such as
> [https://github.com/apache/fineract/pull/1171/files] and
> [https://github.com/apache/fineract/pull/1123/files] re. FINERACT-854, I've
> learnt about Fineract's support for an {{sqlSearch}} parameter on a number of
> its APIs, such as {{/clients}} (and others).
> According to
> [https://demo.fineract.dev/fineract-provider/api-docs/apiLive.htm] :
> {quote}_sqlSearch
> String optional
> Use an sql fragment valid for the underlying client schema to filter
> results. e.g. display_name like %K%
> {quote}
> [https://github.com/apache/fineract/search?p=2&q=sqlSearch&unscoped_q=sqlSearch]
> shows all current occurrences. There are a number, but not THAT many either.
> (By far not every API supports this, only a handful.)
> This can be used e.g. like this:
> [https://demo.fineract.dev/fineract-provider/api/v1/clients?paged=true&sqlSearch=c.account_no=3&tenantIdentifier=default]
> To me, this is an egregious violation of "layering architecture". Basically,
> the REST API gives you direct SQL database access! You apparently have to
> know the exact name of not the SQL table but the alias used in the respective
> internally hard-coded query (note the use of {{c.}} in the example above, NOT
> {{m_client}}), and the internal SQL column name (note the use of
> {{account_no}}, NOT {{accountNo}}). There is no real documentation how to use
> this, and even if there were, in my tests I've noticed its fairly easy to
> provoke _500 Internal Server Errors_ when using {{sqlSearch}} with a slightly
> wrong syntax.
> From a security point of view, it's not quite as bad as it looks, because
> there is code with heuristics to "validate" the {{sqlSearch}} and prevent SQL
> Injections. But that could have holes (I don't want to know!), so... this
> still isn't great, at all, IMHO.
> From a performance point of view, permitting clients to run arbitrary queries
> isn't great either. You can't really reliable offer performance guarantees,
> or offer tuning with indices, if at the end of the day the wide open API just
> lets a client "query whatever they want" anyway.
> Use of {{sqlSearch}} by (public) API clients isn't that hard to find. I did
> some digging, and:
> * The new web-app UI doesn't use sqlSearch (or not yet), see
> [https://github.com/openMF/web-app/search?q=sqlSearch&unscoped_q=sqlSearch]
> * The old community-app UI does use sqlSearch, see
> [https://github.com/openMF/community-app/search?p=1&q=sqlSearch&unscoped_q=sqlSearch].
> But only in 2 very specific places, for Loans' {{l.loan_status_id in
> (100,200)}} and Clients' {{c.status_enum=100}}. This was apparently
> introduced by [~vishwasbabu] in
> [https://github.com/openMF/community-app/pull/1582|https://github.com/openMF/community-app/pull/1582/files]
> for [MIFOSX-2712.|https://mifosforge.jira.com/browse/MIFOSX-2712.] It's
> noteworthy that the Find on
> [https://cui.fineract.dev/.../clients|https://cui.fineract.dev/?baseApiUrl=https://demo.fineract.dev&tenantIdentifier=default#/clients]
> does NOT use {{sqlSearch}} but the [/search
> API|https://demo.fineract.dev/fineract-provider/api-docs/apiLive.htm#search]
> * other repos on openMF, such as Mobile Apps & Co, don't realy seem to
> actively use {{sqlSearch}}, looking at
> [https://github.com/search?p=7&q=org%3AopenMF+sqlSearch&type=Code]
> Other than that, I don't know if anyone actively using {{sqlSearch}} would
> have any major objections to... just simply altogether removing this
> entirely? Folks may of course be using this in their own client UIs, but...
> they really shouldn't, this is a "bad" API. If you are missing a query
> facility, just contribute to the upstream project and raise a pull request to
> add whatever query option you are missing to whatever Fineract API (such as
> e.g. by status for Loans and Clients).
> Let's further discuss on the developer mailing list on thread "Use of
> sqlSearch argument in Groups/Clients List" if anyone wants to strongly defend
> {{sqlSearch}}. If not, let's just completely remove it. We do have to first
> replace the small current use in the community-app.
> PS: Nota bene that this issue isn't stating that a RES
[jira] [Updated] (FINERACT-1289) Tax component not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1289: --- Fix Version/s: (was: 1.10.0) > Tax component not working as expected > - > > Key: FINERACT-1289 > URL: https://issues.apache.org/jira/browse/FINERACT-1289 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges >Affects Versions: 1.4.0 >Reporter: Bharath Gowda >Assignee: Chirag Gupta >Priority: Major > Fix For: 1.11.0 > > Attachments: loan charge config.png, loan charge split not > happening.png, loan product config -1.png, loan product config -2.png, tax > component config.jpeg, tax group config.png > > > tax attached to the loan charge is not getting affected at the > loan/accounting level > To reproduce > 1. Create a tax component-> create a tax group with the component created. > 2. Create loan charge(any parameter, refer to the attachment for the > parameters I used) and map the tax group created. > 3. Add the charge to the loan product (with periodic accrual accounting) > enabled > 4. create/approve/disburse a loan from that loan product. > 5. Ideally the charge with the tax attached should have JE splits for charge > amount and tax amount separated. > But the tax bifurcation is not happening > > Have attached > product config screenshot, charge config screenshot, tax config screenshot, > and loan issue screenshot for more understanding > Please add a comment if you need any help > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1703) Deactivating a system user
[ https://issues.apache.org/jira/browse/FINERACT-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1703: --- Fix Version/s: (was: 1.10.0) > Deactivating a system user > -- > > Key: FINERACT-1703 > URL: https://issues.apache.org/jira/browse/FINERACT-1703 > Project: Apache Fineract > Issue Type: Improvement > Components: Security >Affects Versions: 1.7.0 >Reporter: ibrahim kimbugwe >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2022-08-21-18-18-58-042.png > > > As a security measure, organisations from time to time change employees. This > means users are created and sometimes deleted or deactivated. Such cases may > include an employee under investigation or under temporary suspension. After > issues are sorted, the user has to be activated again. > We need to enhance the system to have a check button for active > !image-2022-08-21-18-18-58-042.png|width=542,height=344! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2028) Have correct Audit Log entries inserted related to Jobs
[ https://issues.apache.org/jira/browse/FINERACT-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2028: --- Fix Version/s: (was: 1.10.0) > Have correct Audit Log entries inserted related to Jobs > --- > > Key: FINERACT-2028 > URL: https://issues.apache.org/jira/browse/FINERACT-2028 > Project: Apache Fineract > Issue Type: Improvement > Components: Job Scheduler >Affects Versions: 1.8.4 >Reporter: Peter Santa >Priority: Major > Labels: BeanSalad > Fix For: 1.11.0 > > > h1. Background > Currently there are no audit logs inserted while running jobs. > h1. Goal > Have correct audit log inserted. > h1. Acceptance Criteria > * there is a log entry in case the job is triggered -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1797) Remove tenant references from cache annotations
[ https://issues.apache.org/jira/browse/FINERACT-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1797: --- Fix Version/s: (was: 1.10.0) > Remove tenant references from cache annotations > --- > > Key: FINERACT-1797 > URL: https://issues.apache.org/jira/browse/FINERACT-1797 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > At the moment pretty much all "@Cache" annotations contain a reference to " > org.apache.fineract.infrastructure.core.service.ThreadLocalContextUtil" to > keep the cache separated by tenant. This makes the code quite unreadable, but > spreads the use of this util class all over the place and makes it quite > impossible to refactor the tenant mechanics. > As a preparation for this (=simplifying the tenant mechanics) the thread > context utility class will be removed from the cache annotations and replaced > with a central Spring Java config. This should also make it easier to split > up the code base into separate modules (one less dependency). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1130) Add ErrorProne's TypeParameterUnusedInFormals
[ https://issues.apache.org/jira/browse/FINERACT-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1130: --- Fix Version/s: (was: 1.10.0) > Add ErrorProne's TypeParameterUnusedInFormals > - > > Key: FINERACT-1130 > URL: https://issues.apache.org/jira/browse/FINERACT-1130 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Assignee: Percy Ashu >Priority: Minor > Fix For: 1.11.0 > > > Following up on FINERACT-822 for [~Percy Ashu] to add > TypeParameterUnusedInFormals some time, if interested (so that we can close > FINERACT-822 for 1.4.0). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1535) Migration from Mifos to Fineract
[ https://issues.apache.org/jira/browse/FINERACT-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1535: --- Fix Version/s: (was: 1.10.0) > Migration from Mifos to Fineract > > > Key: FINERACT-1535 > URL: https://issues.apache.org/jira/browse/FINERACT-1535 > Project: Apache Fineract > Issue Type: Bug > Components: Database, Migration Scripts >Affects Versions: 1.7.0 >Reporter: Sifiso Mtetwa >Assignee: Aleksandar Vidakovic >Priority: Critical > Fix For: 1.11.0 > > Attachments: MifostoFineract.sql > > > Dear All, > > Since Mifos 18.03.01 we have encountered many bugs trying to migrate to > Fineract. This has prohibited some long standing Mifos users to efficiently > move to Fineract without facing some challenges. Some migration scripts have > been included but most schema changes have yet to be dealt with. While some > fixes have been applied to isolated instances there is need to provide > official support to this bug. And to cleanup the current script on the latest > stable release 1.6.0. Therefore using schema diffs and manually debugging we > have come up with a solution providing the entire migration script. > However the tenantUpgradeService obviously includes a good chunk of the > script but a lot is still missing and some of it has code errors. > Can we include this script removing the script that is added already to the > service automatically deployed on startup. Is there a quick way of > identifying which script has been left out from Fineract so that some of the > queries are not duplicated? > Any suggestions and or solutions will be very much appreciated. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1956) Added the skeleton structure necessary to publish doc using Antora
[ https://issues.apache.org/jira/browse/FINERACT-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1956: --- Fix Version/s: (was: 1.10.0) > Added the skeleton structure necessary to publish doc using Antora > -- > > Key: FINERACT-1956 > URL: https://issues.apache.org/jira/browse/FINERACT-1956 > Project: Apache Fineract > Issue Type: New Feature > Components: Docs >Affects Versions: 1.9.0 >Reporter: John Ruhiu >Priority: Major > Fix For: 1.11.0 > > > Currently, documentation is scattered in various platforms(tools) i.e readme, > wiki, project landing page and asciidoc. To streamline documentation, this > task aims to consolidate the relevant content from the various sources into > asciidoc and have docs as code which will be easier to create, update, > version control and so on. > This task creates the initial structure necessary to publish asciidoc files > using Antora static site generator. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2083) Balloon repayment amount for Loan account
[
https://issues.apache.org/jira/browse/FINERACT-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-2083:
---
Fix Version/s: (was: 1.9.0)
(was: 1.10.0)
> Balloon repayment amount for Loan account
> -
>
> Key: FINERACT-2083
> URL: https://issues.apache.org/jira/browse/FINERACT-2083
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Loan
>Reporter: Jose Alberto Hernandez
>Priority: Minor
> Fix For: 1.11.0
>
>
> Balloon repayment amount for Loan account
> A balloon payment is {*}the final amount due on a loan that is structured as
> a series of small monthly payments followed by a single much larger sum at
> the end of the loan period{*}. The early payments may be all or almost all
> payments of interest owed on the loan, with the balloon payment being the
> principal of the loan.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1980) 4-eye checker user can approve their own make command
[
https://issues.apache.org/jira/browse/FINERACT-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1980:
---
Fix Version/s: (was: 1.10.0)
> 4-eye checker user can approve their own make command
> -
>
> Key: FINERACT-1980
> URL: https://issues.apache.org/jira/browse/FINERACT-1980
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.9.0
>Reporter: Peter Santa
>Priority: Major
> Fix For: 1.11.0
>
>
> h1. Steps to reproduce
> * Enable maker-checker functionality and create a role with permission to
> make and check journal entries
> * Create a journal entry
> * Send approval for create journal entry command (POST
> /makercheckers/\{{original make journal entry command ID}}?command=approve)
> h1. Expected results
> Check request for own command cannot be executed
> h1. Real results
> Check request for own command can be executed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1249) Re-introduce type safety in JAX-RS resource classes
[ https://issues.apache.org/jira/browse/FINERACT-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1249: --- Fix Version/s: (was: 1.10.0) > Re-introduce type safety in JAX-RS resource classes > --- > > Key: FINERACT-1249 > URL: https://issues.apache.org/jira/browse/FINERACT-1249 > Project: Apache Fineract > Issue Type: Bug > Components: SDK >Reporter: Michael Vorburger >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > I'll raise a PR to add the https://github.com/swagger-api/validator-badge to > the top of our README. > It will show that our Swagger is currently INVALID, > https://validator.swagger.io/validator/debug?url=https://demo.fineract.dev/fineract-provider/swagger-ui/fineract.yaml > shows why. > The goal of this issue is to resolve all problems causing Swagger validation > error and get that badge on the README to turn green. > [~aleks] or [~ptuomola] or [~sanyam] ([~sanyam96]?) or [~Grandolf49] or > [~manthan] perhaps this is something one of you would be interested in > resolving? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1322) Add Support for a Bi Monthly Loan Product
[ https://issues.apache.org/jira/browse/FINERACT-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1322: --- Fix Version/s: (was: 1.10.0) > Add Support for a Bi Monthly Loan Product > - > > Key: FINERACT-1322 > URL: https://issues.apache.org/jira/browse/FINERACT-1322 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Affects Versions: 1.8.0 >Reporter: Yemdjih Kaze Nasser >Priority: Major > Fix For: 1.11.0 > > > Add the ability to create a loan that is collected twice a month. Date > selection would be one of two options > Two dates selected for each month: default dates are already part of this > ensemble i.e 15th and 30th, 10th and 25th > These date combinations may change midway for e,g 10/25 may become 15/30, > Which means we can edit the loan product’ First and second date thus > affecting the schedule change from that day. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2059) Re-Aging of overdue loan (aka settlement plan)
[ https://issues.apache.org/jira/browse/FINERACT-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2059: --- Fix Version/s: (was: 1.10.0) > Re-Aging of overdue loan (aka settlement plan) > -- > > Key: FINERACT-2059 > URL: https://issues.apache.org/jira/browse/FINERACT-2059 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Mihaly Dallos >Assignee: Mihaly Dallos >Priority: Major > Labels: PepperSoup > Fix For: 1.11.0 > > > h3. Re-aging > Re-aging also known as Settlement Plan is to assist customers who are in > duress around repaying their loans; > The goal is to create a new set of Installments for the same loan account > from the principal outstanding pending on the loan account > For example, for a customer who is severely behind on payments, they could > agree to a settlement plan where instead of having to pay now, it could be > spread over the next 12 months, paying back the remaining 750 euro balance > but over 10 equal payments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1698) Prompt user to confirm Password before changing password
[ https://issues.apache.org/jira/browse/FINERACT-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1698: --- Fix Version/s: (was: 1.10.0) > Prompt user to confirm Password before changing password > > > Key: FINERACT-1698 > URL: https://issues.apache.org/jira/browse/FINERACT-1698 > Project: Apache Fineract > Issue Type: Improvement > Components: Security >Affects Versions: 1.7.0 >Reporter: ibrahim kimbugwe >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2022-08-21-12-48-27-080.png > > > Upon updating the password inside the user profile, a user needs to be > prompted his/her current password. > Let's take a scenario of a user finishing work in the evening and forgets to > logout of the system, the current session is 5 minutes whereby if someone > gets onto the user's computer while logged in, he/she can change the password > since the system allows to change a password without need to confirm the old > password. > !image-2022-08-21-12-48-27-080.png|width=554,height=280! > This is a big security issue since the user's changed credentials can be used > even off the current PC to maliciously cause harm. > [~edcable] [~aleks], [~francisguchie] [~rrpawar] & [~eroemma] what is your > opinion on this and can it receive attention please? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1540) Rounding Mode unable to change from default 6
[ https://issues.apache.org/jira/browse/FINERACT-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1540: --- Fix Version/s: (was: 1.10.0) > Rounding Mode unable to change from default 6 > - > > Key: FINERACT-1540 > URL: https://issues.apache.org/jira/browse/FINERACT-1540 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, System >Affects Versions: 1.7.0 >Reporter: Sifiso Mtetwa >Priority: Blocker > Labels: LOAN > Fix For: 1.11.0 > > Attachments: roundingmode.jpg, roundingmodeerror.jpg > > > If you create a product with Declining balance and Equal Amortisation the > scheduled repayments are never consistently equal. This is because Rounding > mode is currently a default of 6 in Global configurations. However if you > would like to change it to > > HALF_DOWN: If the discarded digit is .5 or lower, the last digit is rounded > down. > HALF_UP: If the discarded digit is .5 or greater, the next digit is rounded > up. > FLOOR: Rounds down to the nearest digit even if the discarded digit is .5 or > greater. > CEILING: If the discarded digit is anything but zero, the next digit is > rounded up. > as in this ticket [https://mifosforge.jira.com/browse/MIFOSX-858] > > Currently if you try and change to another value other than 6 it fails with > error "Unable to modify this configuration as it is a trap door > configuration. - " > This issue dates as far back as 2014 and still persists in Fineract 1.6.0. Is > there a fix for this issue or if there are any branches that have solved this > that we can merge. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2038) Upgrade to Spring Boot 3.2.x
[ https://issues.apache.org/jira/browse/FINERACT-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2038: --- Fix Version/s: (was: 1.10.0) > Upgrade to Spring Boot 3.2.x > > > Key: FINERACT-2038 > URL: https://issues.apache.org/jira/browse/FINERACT-2038 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2109) Java libraries dependencies versions between modules
[ https://issues.apache.org/jira/browse/FINERACT-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2109: --- Fix Version/s: (was: 1.10.0) > Java libraries dependencies versions between modules > > > Key: FINERACT-2109 > URL: https://issues.apache.org/jira/browse/FINERACT-2109 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Jose Alberto Hernandez >Priority: Minor > Fix For: 1.11.0 > > > *Background* > Fineract modules have inconsistent Spring and other library versions. > This can cause random issues like a LoanCOBManagerConfiguration.class class > loading error. > The following command can be used to check lib versions: > ./gradlew dependencyReport > Investigate why the library versions are different and ensure that the > modules are using the same library versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1699) Print Submitted collection sheet
[ https://issues.apache.org/jira/browse/FINERACT-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1699: --- Fix Version/s: (was: 1.10.0) > Print Submitted collection sheet > > > Key: FINERACT-1699 > URL: https://issues.apache.org/jira/browse/FINERACT-1699 > Project: Apache Fineract > Issue Type: Improvement > Components: Groups >Affects Versions: 1.7.0 >Reporter: ibrahim kimbugwe >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2022-08-21-14-55-53-508.png > > > On submitting a collection sheet, the system posts the money to the > respective accounts. There is however no check to see the submitted sheet > after submission. > !image-2022-08-21-14-55-53-508.png|width=558,height=480! > We are looking at a scenario where the system user posts the correct figures > to the wrong person. All the validations are okay with the totals matching. > This would mean that customer A gets money that was supposed to be posted > onto customer B and vice versa. We need to have a printout either before > submission or after submission to be verified and filed by the organisation. > This will go further to enable the organisation to handle customers' issues > related to mismatching figures with their passbooks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1142) Recommend OAuth security for production installations
[ https://issues.apache.org/jira/browse/FINERACT-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1142: --- Fix Version/s: (was: 1.10.0) > Recommend OAuth security for production installations > - > > Key: FINERACT-1142 > URL: https://issues.apache.org/jira/browse/FINERACT-1142 > Project: Apache Fineract > Issue Type: Sub-task > Components: Security >Affects Versions: 1.8.0 >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > [~awasum] [~edcable] a reminder of our recent discussion as suggested by > Awasum -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1631) Illegal value for dayofmonth issue Fineract 1.7
[ https://issues.apache.org/jira/browse/FINERACT-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1631: --- Fix Version/s: (was: 1.10.0) > Illegal value for dayofmonth issue Fineract 1.7 > --- > > Key: FINERACT-1631 > URL: https://issues.apache.org/jira/browse/FINERACT-1631 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.7.0, 1.8.0 > Environment: Windows server 2023, tomcat 9, Mysql 8, Java 17 >Reporter: Chantilly Muyaya >Priority: Major > Fix For: 1.11.0 > > > > After one month of Fineract 1.7.0 deployment with Mifos community app for > front-end, everything was working well. > At June 1 2022, I raise this exception, "illegal value for dayofmonth field, > value 31 is not valid for month June" when I try to create saving account or > saving product. But for other product or account type everything worked well. > When I try manually to change the server date to move on month ended with 30 > days the saving account worked correctly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1971) Minor bug-fixes and enhancements of 1.10.0
[ https://issues.apache.org/jira/browse/FINERACT-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1971: --- Fix Version/s: (was: 1.10.0) > Minor bug-fixes and enhancements of 1.10.0 > -- > > Key: FINERACT-1971 > URL: https://issues.apache.org/jira/browse/FINERACT-1971 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Mihaly Dallos >Priority: Minor > Labels: PepperSoup > Fix For: 1.11.0 > > > This issue collects all the tiny PRs which improves Fineract either by > bug-fix or non-significant improvement. This issue gets closed with *1.10* > release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1983) Date handling improvements - general
[ https://issues.apache.org/jira/browse/FINERACT-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1983: --- Fix Version/s: (was: 1.10.0) > Date handling improvements - general > > > Key: FINERACT-1983 > URL: https://issues.apache.org/jira/browse/FINERACT-1983 > Project: Apache Fineract > Issue Type: Task > Components: Loan, Savings >Affects Versions: 1.9.0 >Reporter: Peter Santa >Priority: Major > Labels: BeanSalad > Fix For: 1.11.0 > > > h1. Goal > Separate date handling of savings and loan accounts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1398) Standardize the Character Set and the Collation
[ https://issues.apache.org/jira/browse/FINERACT-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1398: --- Fix Version/s: (was: 1.10.0) > Standardize the Character Set and the Collation > --- > > Key: FINERACT-1398 > URL: https://issues.apache.org/jira/browse/FINERACT-1398 > Project: Apache Fineract > Issue Type: Improvement > Components: Database, Migration Scripts >Affects Versions: 1.8.0 >Reporter: Victor Romero >Priority: Major > Fix For: 1.11.0 > > > It is required to have a Standard in Fineract for handling the Information > entered into the Database so then the Database creation, tables and migration > script should use the Standard Charset and Collation defined for Fineract. > It is proposed to use as Standard in Fineract: utf8mb4 as charset and > utf8mb4_unicode_ci as collation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2037) Make test AdvancedPaymentAllocationLoanRepaymentScheduleTest.uc118() time independent
[ https://issues.apache.org/jira/browse/FINERACT-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2037: --- Fix Version/s: (was: 1.10.0) > Make test AdvancedPaymentAllocationLoanRepaymentScheduleTest.uc118() time > independent > - > > Key: FINERACT-2037 > URL: https://issues.apache.org/jira/browse/FINERACT-2037 > Project: Apache Fineract > Issue Type: Bug >Reporter: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > Currently the test fails when run on certain times of the day (early > afternoon CET?). Can we fix this to avoid falsely failing tests? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1417) Introduce a new pivot date to filter the savings transactions.
[ https://issues.apache.org/jira/browse/FINERACT-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1417: --- Fix Version/s: (was: 1.10.0) > Introduce a new pivot date to filter the savings transactions. > -- > > Key: FINERACT-1417 > URL: https://issues.apache.org/jira/browse/FINERACT-1417 > Project: Apache Fineract > Issue Type: New Feature > Components: Savings >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.11.0 > > > Current fineract code base use multiple for loops to calculate the > transaction related data on a savings transaction. This adds an unnecessary > latency to a transaction request. By introducing a pivot date, this number of > iterations can be reduced with the help of savings account summary available. > However, in this scenario back dated transactions will not be allowed. Since, > there can be scenarios where back dated transactions are needed, a global > configuration is introduced to prevent breaking the existing use cases > completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1950) Disallow backdated transactions - A Global Configuration
[ https://issues.apache.org/jira/browse/FINERACT-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1950: --- Fix Version/s: (was: 1.10.0) > Disallow backdated transactions - A Global Configuration > - > > Key: FINERACT-1950 > URL: https://issues.apache.org/jira/browse/FINERACT-1950 > Project: Apache Fineract > Issue Type: Improvement >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.11.0 > > > We need to have a global configuration to disallow backdated transactions for > a given period without necessarily closing an accounting period in the > closing entries. > A use case of a teller not being allowed to post a backdated transaction on a > customer after the till was balanced or after COB. The accountant can however > have the right to post GL transactions on a back date. > > This should however be set as a global configuration that can be turned on > and off. > > [~francisguchie] and [~bgowda] and [~eroemma] what do you think of this > improvement? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1701) Printing posted GL transaction
[ https://issues.apache.org/jira/browse/FINERACT-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1701: --- Fix Version/s: (was: 1.10.0) > Printing posted GL transaction > -- > > Key: FINERACT-1701 > URL: https://issues.apache.org/jira/browse/FINERACT-1701 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.7.0 >Reporter: ibrahim kimbugwe >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2022-08-21-15-48-58-982.png, > image-2022-08-21-15-51-34-946.png, image-2022-08-21-15-55-06-535.png > > > In the normal Banking environment, accounting is controlled by maker and > checker where the finance assistant posts transactions then the Finance > manager approves them. Such a transaction is stamped and filled for reference > before being approved in the system. > Workflow > !image-2022-08-21-15-48-58-982.png|width=547,height=100! > We need to add a printing functionality between the approval and the creation > of the entry > !image-2022-08-21-15-55-06-535.png|width=554,height=110! > This will help in the approval process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1184) Simple Interest Functionality
[ https://issues.apache.org/jira/browse/FINERACT-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1184: --- Fix Version/s: (was: 1.10.0) > Simple Interest Functionality > - > > Key: FINERACT-1184 > URL: https://issues.apache.org/jira/browse/FINERACT-1184 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.8.0 >Reporter: Airsay >Priority: Major > Fix For: 1.11.0 > > > Simple Interest. While not widely used across FI, there are some clients that > don't compound interest. I've seen in the code-base that there were plans for > simple interest. I would like to see this in v1.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1621) All transaction date should be set to current date place holders
[ https://issues.apache.org/jira/browse/FINERACT-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1621: --- Fix Version/s: (was: 1.10.0) > All transaction date should be set to current date place holders > > > Key: FINERACT-1621 > URL: https://issues.apache.org/jira/browse/FINERACT-1621 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.8.0 >Reporter: ibrahim kimbugwe >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.11.0 > > Attachments: loan repayment issue.JPG > > > At loan repayment, the system selects the proposed repayment date as per the > repayment schedule. I believe this should not be the case as the transaction > date always changes as many loans are not repaid at the proposed scheduled > date as they may pay before or after. To reduce errors when selecting the > transaction date, the system should pick the current date by default and > allow adjustments if it is a backdated transaction. > !loan repayment issue.JPG|width=652,height=304! > [~francisguchie] [~eroemma] & [~mkaitesi] what's your take on this? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2086) Fix Savings Account Closure error
[
https://issues.apache.org/jira/browse/FINERACT-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-2086:
---
Fix Version/s: (was: 1.10.0)
> Fix Savings Account Closure error
> -
>
> Key: FINERACT-2086
> URL: https://issues.apache.org/jira/browse/FINERACT-2086
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.9.0
>Reporter: Kigenyi Wilfred
>Priority: Minor
> Fix For: 1.11.0
>
>
> Sometimes when closing a savings a account a ClassCastException is raised and
> results from attempting to cast a Short value to an Integer in
> AccountAssociationsReadPlatformServiceImpl.java
> AccountAssociationType associationType =
> AccountAssociationType.fromInt((Integer)
> statusMap.get({color:#6a8759}"type"{color})){color:#cc7832};{color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1183) Ability to archive Fixed Deposit and recurring Deposit Products
[ https://issues.apache.org/jira/browse/FINERACT-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1183: --- Fix Version/s: (was: 1.10.0) > Ability to archive Fixed Deposit and recurring Deposit Products > --- > > Key: FINERACT-1183 > URL: https://issues.apache.org/jira/browse/FINERACT-1183 > Project: Apache Fineract > Issue Type: New Feature >Affects Versions: 1.8.0 >Reporter: Airsay >Priority: Major > Fix For: 1.11.0 > > > We should be able to archive Fixed Deposit and recurring deposit products > products like we have for loan products. When a product is no longer offered > by the FI, we should be able to mark that product as archived so that no new > accounts can be created for that product. > > A possible alternative is to include FD and RD in the Office–.Products Entity > to Entity Mapping. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2002) Manage external IDs: Client
[ https://issues.apache.org/jira/browse/FINERACT-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2002: --- Fix Version/s: (was: 1.10.0) > Manage external IDs: Client > --- > > Key: FINERACT-2002 > URL: https://issues.apache.org/jira/browse/FINERACT-2002 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Adam Saghy >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1664) Wrong Number of clients in a center
[ https://issues.apache.org/jira/browse/FINERACT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1664: --- Fix Version/s: (was: 1.10.0) > Wrong Number of clients in a center > > > Key: FINERACT-1664 > URL: https://issues.apache.org/jira/browse/FINERACT-1664 > Project: Apache Fineract > Issue Type: Bug > Components: Groups >Affects Versions: 1.7.0, 1.8.0 >Reporter: ibrahim kimbugwe >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2022-07-08-20-36-53-060.png > > > The number of clients in a center is wrong at the center details panel. It is > supposed to show the number of groups multiplied by the number of individual > members in individual groups. > !image-2022-07-08-20-36-53-060.png|width=534,height=303! > > [~francisguchie] , [~rrpawar] and [~eroemma] have you seen this issue? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2006) Forgot password on login page
[ https://issues.apache.org/jira/browse/FINERACT-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2006: --- Fix Version/s: (was: 1.10.0) > Forgot password on login page > - > > Key: FINERACT-2006 > URL: https://issues.apache.org/jira/browse/FINERACT-2006 > Project: Apache Fineract > Issue Type: New Feature >Reporter: John Ruhiu >Priority: Major > Fix For: 1.11.0 > > > To do: > # Add a forgot password link on the login page which opens a form to fill > registered user/email > # On submitting the form, fineract will check if the user/email provided is > valid(and active). If valid, send an email with a temporary password will be > sent. The password will have a configurable expiry time > Notes: > A new flag to mark users who have requested for password reset to be added, > this will enforce password reset similar to first time login users. > SCOPE: > 1. Add “Forgot Password” link on the login page > 2. When user clicks it, it opens a simple UI where user enters their email > address. > 3. Verify the email exists if yes, autogenerate password then send it to the > user. > 4. The temp password should have expiry of 24hours > 5. When user tries to reset their password using temp password verify it’s > within 24hrs if yes allow user to reset password. > NOTE: There is functionality already for generating password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1185) Interest Posting on Anniversary Dates
[ https://issues.apache.org/jira/browse/FINERACT-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1185: --- Fix Version/s: (was: 1.10.0) > Interest Posting on Anniversary Dates > - > > Key: FINERACT-1185 > URL: https://issues.apache.org/jira/browse/FINERACT-1185 > Project: Apache Fineract > Issue Type: New Feature >Affects Versions: 1.8.0 >Reporter: Airsay >Priority: Critical > Fix For: 1.11.0 > > > "Anniversary" Interest posting period. Some clients don't necessarily post > interest on the last day of the week, or month or quarter. What they do is > post interest on the "anniversary" date. So for a fixed deposit or recurring > deposit account opened on the 1st of the month, interest is posted on the > first of the month for monthly interests. Those opened say on the 29th are > posted on the 29th (or the last day of the month if that month doesn't have > 29 days like February). A similar thing is done for quarterly or bi-annual > postings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1403) Advance repayment issue after loan rescheduling
[ https://issues.apache.org/jira/browse/FINERACT-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1403: --- Fix Version/s: (was: 1.10.0) > Advance repayment issue after loan rescheduling > --- > > Key: FINERACT-1403 > URL: https://issues.apache.org/jira/browse/FINERACT-1403 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: Bharath Gowda >Assignee: Avik Ganguly >Priority: Major > Fix For: 1.11.0 > > Attachments: after advance repayment.png, before advance > repayment.png, product configuration.png > > > The loan repayment schedule is calculating the wrong principal when advance > payment is done after the loan reschedule is done. > > To reproduce, > 1. Create a loan product as per the shared screenshot > 2. Create a loan account and reschedule any installment and make the payment > for the rescheduled date > 3. Make an advance payment for an installment (for any installment after the > rescheduled installment) > Issue > when advance payment is done, the system is changing the principal amount, > and in turn, the installment is still not completely paid > because of this, the loan is considered overdue even if the payment is done > on/before time. > > Please find the example screenshot attached of the issue loan with complete > explanation and expected result > please do let me know if you need any more clarification -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2056) Introduce Lombok to savings module
[ https://issues.apache.org/jira/browse/FINERACT-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2056: --- Fix Version/s: (was: 1.10.0) > Introduce Lombok to savings module > -- > > Key: FINERACT-2056 > URL: https://issues.apache.org/jira/browse/FINERACT-2056 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Pushkal Mudhapaka >Priority: Major > Fix For: 1.11.0 > > > This sub-task introduces Lombok annotations in savings module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1519) Fineract.dev CD is no longer auto-updating
[ https://issues.apache.org/jira/browse/FINERACT-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1519: --- Fix Version/s: (was: 1.10.0) > Fineract.dev CD is no longer auto-updating > -- > > Key: FINERACT-1519 > URL: https://issues.apache.org/jira/browse/FINERACT-1519 > Project: Apache Fineract > Issue Type: Bug >Reporter: Michael Vorburger >Assignee: Michael Vorburger >Priority: Major > Fix For: 1.11.0 > > > https://github.com/vorburger/www.fineract.dev/issues/15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1817) Improve release plugin
[ https://issues.apache.org/jira/browse/FINERACT-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1817: --- Fix Version/s: (was: 1.10.0) > Improve release plugin > -- > > Key: FINERACT-1817 > URL: https://issues.apache.org/jira/browse/FINERACT-1817 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > Fix For: 1.11.0 > > > * add CVE email to announce and dev list > * improve maintenance release workflow > * create "maintenance/1.x" branches > * finish SVN step (add artifacts and commit) > * fix configured email recipients > * input validation > * close releases in Jira with API call > * introduce wizard? > Implement the following steps: > * Release step 2 > * Release step 4 > * Release step 9 > * Release step 13 > * Release step 14 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2069) QueryDSL migration: Field Configuration Service
[ https://issues.apache.org/jira/browse/FINERACT-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2069: --- Fix Version/s: (was: 1.10.0) > QueryDSL migration: Field Configuration Service > --- > > Key: FINERACT-2069 > URL: https://issues.apache.org/jira/browse/FINERACT-2069 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1245) Error Prone Bug Pattern JavaTimeDefaultTimeZone should be Error not just Warning
[
https://issues.apache.org/jira/browse/FINERACT-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1245:
---
Fix Version/s: (was: 1.10.0)
> Error Prone Bug Pattern JavaTimeDefaultTimeZone should be Error not just
> Warning
>
>
> Key: FINERACT-1245
> URL: https://issues.apache.org/jira/browse/FINERACT-1245
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Michael Vorburger
>Assignee: Aleksandar Vidakovic
>Priority: Minor
> Fix For: 1.11.0
>
>
> This should be configured to be an Error, not just a Warning, and the
> occurrence fixed:
> {noformat}> Task :fineract-client:compileTestJava
>
> /home/vorburger/dev/Mifos/fineract/fineract-client/src/test/java/org/apache/fineract/integrationtests/newstyle/OfficeTest.java:40:
> warning: [JavaTimeDefaultTimeZone] LocalDate.now() is not allowed because it
> silently uses the system default time-zone. You must pass an explicit
> time-zone (e.g., ZoneId.of("America/Los_Angeles")) to this method.
>
>
> .openingDate(LocalDate.now()).dateFormat(dateFormat()).locale("en_US"))).getOfficeId()).isGreaterThan(0);
>
> ^
>
> (see https://errorprone.info/bugpattern/JavaTimeDefaultTimeZone)
>
> Did you mean
> '.openingDate(LocalDate.now(ZoneId.systemDefault())).dateFormat(dateFormat()).locale("en_US"))).getOfficeId()).isGreaterThan(0);'?
>
>
> 1 warning{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-2039) Swagger fix - SavingsAccountsApiResourceSwagger.GetSavingsAccountsResponse
[
https://issues.apache.org/jira/browse/FINERACT-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-2039:
---
Fix Version/s: (was: 1.10.0)
> Swagger fix - SavingsAccountsApiResourceSwagger.GetSavingsAccountsResponse
> --
>
> Key: FINERACT-2039
> URL: https://issues.apache.org/jira/browse/FINERACT-2039
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Peter Santa
>Priority: Major
> Fix For: 1.11.0
>
>
> {color:#1d1c1d}GET /savingsaccounts{color}
> {color:#1d1c1d}SavingsAccountsApiResourceSwagger.GetSavingsAccountsResponse{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1307) Loan Ideal disbursement to calculation cause to wrong interest rate
[
https://issues.apache.org/jira/browse/FINERACT-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1307:
---
Fix Version/s: (was: 1.10.0)
> Loan Ideal disbursement to calculation cause to wrong interest rate
>
>
> Key: FINERACT-1307
> URL: https://issues.apache.org/jira/browse/FINERACT-1307
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: eitan frailich
>Assignee: eitan frailich
>Priority: Minor
> Fix For: 1.11.0
>
> Attachments: image-2021-02-02-16-43-07-381.png
>
>
> *ISSUE*
> My issue/bug happens when I am setting "First repayment on" field I get a
> repayment schedule with a wrong interest rate for the first installment.
> Example: When I set "First repayment on" to 01/02/21 and expected
> disbursement is 27/1/21(Frist image) then I get the wrong interest.The first
> installment interest is 21,232.88$ (second Image) - calculated for the entire
> month (31 days) instead of 5 days (the time from the disbursement to the
> first repayment), the right interest should be 3424.75$.
> *After debugging:*
> In AbstractLoanScheduleGenerator there is a function
> {{calculateInterestStartDateForPeriod}} - it uses the {{idealDisbursment}}
> for setting the interest start date for the first installment, The
> {{idealDisbursment}} is calculated by
> {{idealDisbursementDateBasedOnFirstRepaymentDate}} which does
> [{{firstRepaymentDate}} - 1 repayment Period Frequency] aka, for 01/02/21
> with months as repyment frequency it will return 01/01/21.
> So when we dont set the "First repayment on" the {{idealDisbursment}} will be
> the expected disbursement date because the first repayment is always
> {{expectedDisbursment}}+1. But if we set the "First repayment on" we get the
> wrong value for the {{idealDisbursment}} - in my example we got 01/0/21 and
> this is why the first installment interest was calculated for an entire month
> instead of 5 days.
> *Is it a bug or not?*
> I am not sure why {{idealDisbursementDateBasedOnFirstRepaymentDate}} exists,
> the simple solution is to do idealDisbursment=expectedDisbursmentDate.I
> tried it locally and looks like it works, I will be happy to make a PR, but
> want to make sure indeed that the
> {{idealDisbursementDateBasedOnFirstRepaymentDate}} is redundant.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1559) New response parameters required for Loan creation response/retrieve loan information API
[
https://issues.apache.org/jira/browse/FINERACT-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1559:
---
Fix Version/s: (was: 1.10.0)
> New response parameters required for Loan creation response/retrieve loan
> information API
> --
>
> Key: FINERACT-1559
> URL: https://issues.apache.org/jira/browse/FINERACT-1559
> Project: Apache Fineract
> Issue Type: Improvement
>Affects Versions: 1.6.0
>Reporter: Ed Cable
>Priority: Major
> Fix For: 1.11.0
>
>
> For the following API,
> GET:
> _[https://DomainName/fineract-provider/api/v1/loans/\|https://domainname/fineract-provider/api/v1/loans/]{loanId}?associations=all&exclude=guarantors,futureSchedule_
> The loan creation response and retrieve loan information requires the
> following additional parameters to be returned:
>
> |New Parameter|Value/Amount|
> |available_disbursement_amount|It is the difference of approved amount and
> disbursed amount|
> |past_due_days|No of days the loan is overdue,current date - duedate|
> |next_payment_due_date|Based on the current date, need to populate the next
> payment due date|
> |delinquent_days|No of days the loan is in arrears, current date -
> duedate-grace period|
> |delinquent_date|Date the loan is in arrears, current date - duedate-grace
> period|
> |delinquent_amount|amount overdue after the grace period|
> |last_payment_date|last repayment made date on the loan|
> |last_payment_amount|last repayment amount made date on the loan|
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-2061) Introduce Lombok to the Core module (infrastructure/dataqueries)
[
https://issues.apache.org/jira/browse/FINERACT-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-2061:
---
Fix Version/s: (was: 1.10.0)
> Introduce Lombok to the Core module (infrastructure/dataqueries)
>
>
> Key: FINERACT-2061
> URL: https://issues.apache.org/jira/browse/FINERACT-2061
> Project: Apache Fineract
> Issue Type: Sub-task
>Reporter: Zeyad Nasef
>Priority: Major
> Fix For: 1.11.0
>
>
> h3. *This task introduces Lombok annotations (Getter & AllArgsConstructor) to
> fineract-core module.*
> h3. The following are done:
> *• Refactoring in {{ReportParameterJoinData}} Class:*
> * Removed the getter method from the {{ReportParameterJoinData}} class and
> replaced it with the {{@Getter}} annotation.
> *• Constructor Modification in {{ReportParameterJoinData}} Class:*
> * Removed the class constructor and replaced it with the
> {{@AllArgsConstructor}} annotation.
> *• Backward Compatibility:*
> * Ensured backward compatibility with other classes that use
> {{{}ReportParameterJoinData{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1221) Fineract Client Java SDK API has broken methods
[
https://issues.apache.org/jira/browse/FINERACT-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1221:
---
Fix Version/s: (was: 1.10.0)
> Fineract Client Java SDK API has broken methods
> ---
>
> Key: FINERACT-1221
> URL: https://issues.apache.org/jira/browse/FINERACT-1221
> Project: Apache Fineract
> Issue Type: Bug
> Components: SDK
>Affects Versions: 1.8.0
>Reporter: Michael Vorburger
>Priority: Blocker
> Fix For: 1.11.0
>
>
> Our brand new "Fineract Client Java SDK API" emerging from
> https://github.com/apache/fineract/pull/1428/ for FINERACT-1216 contains at
> least some annotated Java methods which are invalid for Retrofit.
> When enabling {{apiClient.getAdapterBuilder().validateEagerly(true);}}, I'm
> seeing e.g.
> {noformat}java.lang.IllegalArgumentException: Non-body HTTP method cannot
> contain @Body.
> for method ClientApi.delete9
> at retrofit2.Utils.methodError(Utils.java:54)
> at retrofit2.Utils.methodError(Utils.java:43)
> at retrofit2.RequestFactory$Builder.build(RequestFactory.java:213)
> at retrofit2.RequestFactory.parseAnnotations(RequestFactory.java:67)
> at retrofit2.ServiceMethod.parseAnnotations(ServiceMethod.java:26)
> at retrofit2.Retrofit.loadServiceMethod(Retrofit.java:202)
> at retrofit2.Retrofit.validateServiceInterface(Retrofit.java:189)
> at retrofit2.Retrofit.create(Retrofit.java:141)
> at
> org.apache.fineract.client.ApiClient.createService(ApiClient.java:127)
> at
> org.apache.fineract.client.util.FineractClient.createService(FineractClient.java:42)
> at
> org.apache.fineract.client.test.FineractClientTest.testRetrieveAllClients(FineractClientTest.java:41){noformat}
> As a first step to eventually fixing this (and having non-regression for it),
> I'll write an automated test about it (but keep it ignored, for now).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1131) Add Checkstyle IllegalCatch
[ https://issues.apache.org/jira/browse/FINERACT-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1131: --- Fix Version/s: (was: 1.10.0) > Add Checkstyle IllegalCatch > --- > > Key: FINERACT-1131 > URL: https://issues.apache.org/jira/browse/FINERACT-1131 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Assignee: Manthan Surkar >Priority: Minor > Fix For: 1.11.0 > > > Following up on FINERACT-942 for [~Manthan] to add > TypeParameterUnusedInFormals some time, if interested (so that we can close > FINERACT-942 for 1.4.0 now). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1978) Delete data table does not delete references
[ https://issues.apache.org/jira/browse/FINERACT-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1978: --- Fix Version/s: (was: 1.10.0) > Delete data table does not delete references > > > Key: FINERACT-1978 > URL: https://issues.apache.org/jira/browse/FINERACT-1978 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Affects Versions: 1.9.0 >Reporter: Peter Santa >Priority: Critical > Labels: BeanSalad > Fix For: 1.11.0 > > > Data table delete API does not delete data table references and after it, no > operations can be performed on any data table. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1102) Swagger Codegen Client JAR should be available on a Maven repo
[ https://issues.apache.org/jira/browse/FINERACT-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1102: --- Fix Version/s: (was: 1.10.0) > Swagger Codegen Client JAR should be available on a Maven repo > -- > > Key: FINERACT-1102 > URL: https://issues.apache.org/jira/browse/FINERACT-1102 > Project: Apache Fineract > Issue Type: Improvement > Components: SDK >Reporter: Michael Vorburger >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > FINERACT-838 contributed Swagger Codegen Client generation. > In order for the JAR built from that to actually be easily usable, we should > "distribute" it... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1750) User permissions not available
[ https://issues.apache.org/jira/browse/FINERACT-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1750: --- Fix Version/s: (was: 1.10.0) > User permissions not available > --- > > Key: FINERACT-1750 > URL: https://issues.apache.org/jira/browse/FINERACT-1750 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.7.0 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.11.0 > > Attachments: client summary-1.png, permissoin error-1.png > > > We setup users with different permissions. It has come to our attention that > some permissions are not available like the client summary. Others are > available but even when granted, the system does not allow users to access > that information. An example is the client summary and the credit bureau. > !client summary-1.png|width=831,height=378! > !permissoin error-1.png|width=838,height=341! > There is no permission for read credit bureau and client summary. The same > applies to the reports, even when a user is given the rights to view a > report, the system does not show any report unless you give the person the > report super user rights which should not be the case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1436) Support to add Multi Disbursement details on same day
[ https://issues.apache.org/jira/browse/FINERACT-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1436: --- Fix Version/s: (was: 1.10.0) > Support to add Multi Disbursement details on same day > - > > Key: FINERACT-1436 > URL: https://issues.apache.org/jira/browse/FINERACT-1436 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.8.0 >Reporter: Bharath Gowda >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2021-11-08-14-01-38-190.png > > > Support to add Multi Disbursement details on same day > Currently, in a multi disbursement loan account, it is not possible to add > multiple disbursements on the same day. > We need to implement this option to support one of the most common use case > in credit lines or other similar products. > > To reproduce > 1. Create a loan product with multi-tranche enabled > 2. Create a loan account with 1 tranche (with amount lesser than approved > amount) > 3. disburse the loan > 4. Now try to add another tranche for the same day. > the system will not allow adding another tranche on the same day with the > error msg "Tranche disbursement date must be unique -" > !image-2021-11-08-14-01-38-190.png! > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1449) Repayment schedule issue when advance payments are made
[ https://issues.apache.org/jira/browse/FINERACT-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1449: --- Fix Version/s: (was: 1.10.0) > Repayment schedule issue when advance payments are made > --- > > Key: FINERACT-1449 > URL: https://issues.apache.org/jira/browse/FINERACT-1449 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: Bharath Gowda >Assignee: Avik Ganguly >Priority: Critical > Fix For: 1.11.0 > > Attachments: after change.png, before change.png, > loanproductconfiguration.png > > > Repayment schedule issue when advance payments are made > > To reproduce > # create a loan product as attached loan product configuration > # create a loan and disburse on '29 November 2021' for amount 3000 with > First Repayment Date as '03 January 2022' > # Now make a payment of 1 on '02 December 2021' and another payment of 1 on > '03 December 2021' > # Now check the schedule, Installment dates and Interest amount would have > changed. > Check the screenshot of the before and after change attached for reference > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1875) Operation requires a scrollable ResultSet, but this ResultSet is FORWARD_ONLY. Postgres
[
https://issues.apache.org/jira/browse/FINERACT-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1875:
---
Fix Version/s: (was: 1.10.0)
> Operation requires a scrollable ResultSet, but this ResultSet is
> FORWARD_ONLY. Postgres
> ---
>
> Key: FINERACT-1875
> URL: https://issues.apache.org/jira/browse/FINERACT-1875
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Affects Versions: 1.8.3
> Environment: Local:
> - Ubuntu 22.04
> - Postgresql 14.6
> Server:
> - Ubuntu 20.04
> - Postgresql 14.6
> - Tomcat 9.0.71
>Reporter: Richard Matovu
>Priority: Critical
> Labels: postgresql, resultset, scrollable_resultset
> Fix For: 1.11.0
>
>
> Under tax components and tax groups, when you have created more than one
> record of either, and you do a fetch, it throws an error the following error:
> {code:java}
> 2023-01-27 17:41:16.378 -ERROR 22641 --- [nio-443-exec-26]
> o.s.b.w.servlet.support.ErrorPageFilter : Forwarding to error page from
> request [/api/v1/taxes/group] due to exception
> [org.springframework.jdbc.UncategorizedSQLException: StatementCallback;
> uncategorized SQLException for SQL [select tg.id as id, tg.name as
> name,tgm.id as mappingId,tc.id as taxComponentId, tc.name as
> taxComponentName,tgm.start_date as startDate, tgm.end_date as endDate from
> m_tax_group tg inner join m_tax_group_mappings tgm on tgm.tax_group_id =
> tg.id inner join m_tax_component tc on tc.id = tgm.tax_component_id ]; SQL
> state [24000]; error code [0]; Operation requires a scrollable ResultSet, but
> this ResultSet is FORWARD_ONLY.; nested exception is
> org.postgresql.util.PSQLException: Operation requires a scrollable ResultSet,
> but this ResultSet is FORWARD_ONLY.]
> javax.servlet.ServletException:
> org.springframework.jdbc.UncategorizedSQLException: StatementCallback;
> uncategorized SQLException for SQL [select tg.id as id, tg.name as
> name,tgm.id as mappingId,tc.id as taxComponentId, tc.name as
> taxComponentName,tgm.start_date as startDate, tgm.end_date as endDate from
> m_tax_group tg inner join m_tax_group_mappings tgm on tgm.tax_group_id =
> tg.id inner join m_tax_component tc on tc.id = tgm.tax_component_id ]; SQL
> state [24000]; error code [0]; Operation requires a scrollable ResultSet, but
> this ResultSet is FORWARD_ONLY.; nested exception is
> org.postgresql.util.PSQLException: Operation requires a scrollable ResultSet,
> but this ResultSet is FORWARD_ONLY.at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:410)
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
>...Caused by: org.springframework.jdbc.UncategorizedSQLException:
> StatementCallback; uncategorized SQLException for SQL [select tg.id as id,
> tg.name as name,tgm.id as mappingId,tc.id as taxComponentId, tc.name as
> taxComponentName,tgm.start_date as startDate, tgm.end_date as endDate from
> m_tax_group tg inner join m_tax_group_mappings tgm on tgm.tax_group_id =
> tg.id inner join m_tax_component tc on tc.id = tgm.tax_component_id ]; SQL
> state [24000]; error code [0]; Operation requires a scrollable ResultSet, but
> this ResultSet is FORWARD_ONLY.; nested exception is
> org.postgresql.util.PSQLException: Operation requires a scrollable ResultSet,
> but this ResultSet is FORWARD_ONLY.at
> org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTemplate.java:1542)
> at
> org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:393)
> at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:465)
> at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:475)
> at
> org.apache.fineract.portfolio.tax.service.TaxReadPlatformServiceImpl.retrieveAllTaxGroups(TaxReadPlatformServiceImpl.java:80)
> at
> org.apache.fineract.portfolio.tax.api.TaxGroupApiResource.retrieveAllTaxGroups(TaxGroupApiResource.java:91)
> at jdk.internal.reflect.GeneratedMethodAccessor317.invoke(Unknown Source)
>at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ...Caused by: org.postgresql.util.PSQLException: Operation requires a
> scrollable ResultSet, but this ResultSet is FORWARD_ONLY.at
> org.postgresql.jdbc.PgResultSet.checkScrollable(PgResultSet.java:316)at
> org.postgresql.jdbc.PgResultSet.previous(PgResultSet.java:993)at
> com.zaxxer.hikari.pool.HikariProxyResultSet.previous(HikariProxyResultSet.java)
> at
> org.apache.fineract.portfolio.tax.service.TaxReadPlatformServiceImpl$TaxGroupMapper.mapRow(TaxReadPlatformServiceImpl.java:226)
> at
> org.apache.fineract.portfol
[jira] [Updated] (FINERACT-1575) IPv6 Support for deploying Apache Fineract on Serverless Cloud Deployment
[ https://issues.apache.org/jira/browse/FINERACT-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1575: --- Fix Version/s: (was: 1.10.0) > IPv6 Support for deploying Apache Fineract on Serverless Cloud Deployment > - > > Key: FINERACT-1575 > URL: https://issues.apache.org/jira/browse/FINERACT-1575 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Fix For: 1.11.0 > > > When deploying the Apache Fineract in fully managed serverless environment we > got issues because the SpringBoot is requesting a full compliance IPV6 > address, if the address is not following the convention Spring is throwing > exception and then anything from the HTTP will be rejected. > > https://github.com/spring-projects/spring-framework/issues/27013 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1549) Eclipse BIRT reporting module
[ https://issues.apache.org/jira/browse/FINERACT-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1549: --- Fix Version/s: (was: 1.10.0) > Eclipse BIRT reporting module > - > > Key: FINERACT-1549 > URL: https://issues.apache.org/jira/browse/FINERACT-1549 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1790) Reduce compile warnings
[ https://issues.apache.org/jira/browse/FINERACT-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1790: --- Fix Version/s: (was: 1.10.0) > Reduce compile warnings > --- > > Key: FINERACT-1790 > URL: https://issues.apache.org/jira/browse/FINERACT-1790 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > Fix For: 1.11.0 > > > We have currently 30-40 compiler warnings (mostly related to generic types) > that are polluting the compile output... this makes hard so search for errors > when on the command line. > Consider introducing OpenRewrite to help with the refactoring (might not > catch all issues). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1052) Over Payment of loans is Allowed by Default
[ https://issues.apache.org/jira/browse/FINERACT-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1052: --- Fix Version/s: (was: 1.10.0) > Over Payment of loans is Allowed by Default > > > Key: FINERACT-1052 > URL: https://issues.apache.org/jira/browse/FINERACT-1052 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Affects Versions: 1.3.0, 1.4.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Critical > Labels: newbie > Fix For: 1.11.0 > > Attachments: 5.8m Loan Balance.png, 5.8m loan Balance Over Payment > Message.png, Config - Disable Loan Over Payment.jpg, RESTRICTING OVER PAYMENT > OF LOANS.docx > > > Impacted versions: all MifosX versions including latest build > Steps to reproduce: > Select any loan in MifosX and make a payment over and above the dues > Current behavior: > MifosX will accept this > Expected behavior: > We create a global setting where its optional for super user to set allow or > restrict users from over paying loans -- This can be done at global > configurations => -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1976) Read payment type permission not working
[ https://issues.apache.org/jira/browse/FINERACT-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1976: --- Fix Version/s: (was: 1.10.0) > Read payment type permission not working > > > Key: FINERACT-1976 > URL: https://issues.apache.org/jira/browse/FINERACT-1976 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.9.0 >Reporter: Peter Santa >Priority: Critical > Labels: BeanSalad > Fix For: 1.11.0 > > > h1. Steps to reproduce > * Set up a role (non-sys admin) for a user with read permission to payment > types > * Try to read payment types via endpont > h1. Real results > Throws exception stating permission issue > h1. Expected results > User is able to GET payment types -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1561) Add new tagging fields to Data Tables
[
https://issues.apache.org/jira/browse/FINERACT-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1561:
---
Fix Version/s: (was: 1.10.0)
> Add new tagging fields to Data Tables
> -
>
> Key: FINERACT-1561
> URL: https://issues.apache.org/jira/browse/FINERACT-1561
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Data Tables
>Affects Versions: 1.6.0
>Reporter: Ed Cable
>Priority: Major
> Fix For: 1.11.0
>
>
> For retrieiving loan information for clients, we need to add additional
> response parameters to the below API:
>
> GET:
> [_https://DomainName/fineract-provider/api/v1/datatables/\{datatableName}/\{loanId}?genericResultSet=true_|https://domainname/fineract-provider/api/v1/datatables/%7BdatatableName%7D/%7BloanId%7D?genericResultSet=true]
>
> |New Parameter|Value/Amount|
> |tag_added_time|column value added time stamp|
> |tag_removed_time|column value modified time stamp|
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1966) Consolidate committer zone content from various sources into asciidoc
[ https://issues.apache.org/jira/browse/FINERACT-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1966: --- Fix Version/s: (was: 1.10.0) > Consolidate committer zone content from various sources into asciidoc > - > > Key: FINERACT-1966 > URL: https://issues.apache.org/jira/browse/FINERACT-1966 > Project: Apache Fineract > Issue Type: New Feature > Components: Docs >Reporter: John Ruhiu >Priority: Major > Fix For: 1.11.0 > > > Consolidate committer zone content from various sources into asciidoc in > order to have a single source of truth that is easier to maintain. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1808) Fineract Developer Environment
[ https://issues.apache.org/jira/browse/FINERACT-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1808: --- Fix Version/s: (was: 1.10.0) > Fineract Developer Environment > -- > > Key: FINERACT-1808 > URL: https://issues.apache.org/jira/browse/FINERACT-1808 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > We are trying to continuously improve the developer experience e. g. by using > linting tools and automatic formatting tools to ensure a somewhat homogeneous > reading experience. > Just recently "custom modules" were introduced to reduce the amount of guess > work on the developer side how to extend Fineract's default behavior (in the > right way). > It would be great to have a development environment with code generators that > help developers to scaffold extension points, Cucumber and integration tests > etc. We could create either code generators for tools like Yeoman and/or > integrate this even in IDEs like VSCode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1940) Avoid explicit security context usage in REST resource classes
[ https://issues.apache.org/jira/browse/FINERACT-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1940: --- Fix Version/s: (was: 1.10.0) > Avoid explicit security context usage in REST resource classes > -- > > Key: FINERACT-1940 > URL: https://issues.apache.org/jira/browse/FINERACT-1940 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1984) Modular Security Architecture: Phase 1
[
https://issues.apache.org/jira/browse/FINERACT-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1984:
---
Fix Version/s: (was: 1.10.0)
> Modular Security Architecture: Phase 1
> --
>
> Key: FINERACT-1984
> URL: https://issues.apache.org/jira/browse/FINERACT-1984
> Project: Apache Fineract
> Issue Type: Sub-task
>Reporter: Aleksandar Vidakovic
>Assignee: Aleksandar Vidakovic
>Priority: Major
> Fix For: 1.11.0
>
>
> Add Spring Authorization Server as a drop-in replacement for the current
> OAuth support in Fineract ("all batteries included", no separate external ID
> server)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1704) Code cleanup
[ https://issues.apache.org/jira/browse/FINERACT-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1704: --- Fix Version/s: (was: 1.10.0) > Code cleanup > > > Key: FINERACT-1704 > URL: https://issues.apache.org/jira/browse/FINERACT-1704 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Adam Saghy >Assignee: Adam Saghy >Priority: Minor > Fix For: 1.11.0 > > > Doing some cleanup and fix typos. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1310) Accrual transactions not happening for foreclosed loans
[ https://issues.apache.org/jira/browse/FINERACT-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1310: --- Fix Version/s: (was: 1.10.0) > Accrual transactions not happening for foreclosed loans > --- > > Key: FINERACT-1310 > URL: https://issues.apache.org/jira/browse/FINERACT-1310 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Loan >Affects Versions: 1.4.0 >Reporter: Bharath Gowda >Assignee: Nayan Ambali >Priority: Critical > Fix For: 1.11.0 > > > Accrual transactions not happening for foreclosed loans > > To reproduce > 1. Create a loan product(any configuration) with accrual periodic accounting > enabled. > 2. Create/approve/disburse a loan account > 3. foreclose the same loan at any date apart from due date. > 4. loan is getting closed with the interest accrual entry for the foreclosed > transaction > > Expected result, system should post the accrual transaction for the > foreclosed transaction -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1586) Reduce Boilerplate Code by Introducing lombok to Reduce getters/setters and Mapstruct to map REST DTO to Entity Objects
[ https://issues.apache.org/jira/browse/FINERACT-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1586: --- Fix Version/s: (was: 1.10.0) > Reduce Boilerplate Code by Introducing lombok to Reduce getters/setters and > Mapstruct to map REST DTO to Entity Objects > --- > > Key: FINERACT-1586 > URL: https://issues.apache.org/jira/browse/FINERACT-1586 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Rahul Goel >Priority: Minor > Labels: full-time, gsoc2023, mentor > Fix For: 1.11.0 > > > Lombok could help us to not only reduce a large amount of code, but also to > fix a couple of inconsistencies in the code base: > * getters/setters with non-standard characters (e. g. underscores) > * getters/setters with typos > The layered architecture of Fineract requires mapping between REST DTO > classes and internal entity classes. The current code base contains various > strategies to achieve this: > * private functions > * static functions > * mapping classes > All of these approaches are very manual (and error prone) and difficult to > maintain. Mapstruct can help here: > * throw errors at compile time (missing new attributes, type changes etc.) > * one common concept (easier to understand) > * reduce manually maintained code and replace mostly generated code > Challenges: > * maintain immutability (especially in DTO classes) > * should we fluent builder pattern? > * backwards compatibility > * these improvements cannot be introduced as one pull request, but have to > be split up at least at the “module” level (clients, loans, accounts etc.). > This would result in approximately 30 pull requests; if we split up Lombok > and Mapstruct then it would be 30 PRs each (=60); we would need this fine > grained approach to make a transition as painless as possible > * some classes are maybe beyond repair (e. g. Loan.java with 6000 lines of > code, the smaller part getters/setters and a long list of utility/business > logic functions) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1700) Bulk JLG loan Application not displaying loan terms
[ https://issues.apache.org/jira/browse/FINERACT-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1700: --- Fix Version/s: (was: 1.10.0) > Bulk JLG loan Application not displaying loan terms > --- > > Key: FINERACT-1700 > URL: https://issues.apache.org/jira/browse/FINERACT-1700 > Project: Apache Fineract > Issue Type: Bug > Components: Groups >Affects Versions: 1.7.0 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2022-08-21-15-31-25-813.png > > > During the bulk JLG loan application, procedures should follow as per the > documentation here, > [https://docs.mifos.org/mifosx/user-manual/for-operational-users-mifos-x-web-app/accounts-and-transactions/loan-accounts/how-to-process-bulk-jlg-loan-application] > However, after adding client loan amounts and submitting the application, the > system allows the application to go through without returning to the loan > terms page for the individual clients. This means that Incase of a charge > that requires a savings account, the validation will fail since the API does > not return the loan terms window for all the applied loans. > !image-2022-08-21-15-31-25-813.png|width=547,height=376! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1959) Consolidate contributor's zone content from various sources into asciidoc
[ https://issues.apache.org/jira/browse/FINERACT-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1959: --- Fix Version/s: (was: 1.10.0) > Consolidate contributor's zone content from various sources into asciidoc > - > > Key: FINERACT-1959 > URL: https://issues.apache.org/jira/browse/FINERACT-1959 > Project: Apache Fineract > Issue Type: New Feature >Reporter: John Ruhiu >Priority: Major > Fix For: 1.11.0 > > > In order to have comprehensive and cohesive documentation, I am consolidating > content from various sources such as the wiki into asciidoc format which will > then be published using antora static generator. > This ticket covers the consolidation of contributor zone content. The > following sources were used: > * [https://cwiki.apache.org/confluence/display/FINERACT/Contributor%27s+Zone] > * [https://github.com/apache/fineract/blob/develop/CONTRIBUTING.md] > * [https://github.com/apache/fineract/#pull-requests] > * [https://github.com/apache/fineract/#checkstyle-and-spotless] > * [https://github.com/apache/fineract/#logging-guidelines] > * [https://github.com/apache/fineract/#error-handling-guidelines] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1227) Client Java API for binary document files and images are generated wrong
[
https://issues.apache.org/jira/browse/FINERACT-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1227:
---
Fix Version/s: (was: 1.10.0)
> Client Java API for binary document files and images are generated wrong
>
>
> Key: FINERACT-1227
> URL: https://issues.apache.org/jira/browse/FINERACT-1227
> Project: Apache Fineract
> Issue Type: Bug
> Components: SDK
>Affects Versions: 1.8.0
>Reporter: Michael Vorburger
>Priority: Major
> Fix For: 1.11.0
>
>
> The {{org.apache.fineract.client.services.DocumentsApi.downloadFile(String,
> Long, Long)}} (for
> {{_entityType_/_entityId_/documents/_documentId_/attachment}}) returns
> {{Call}}.. it's missing the binary downloaded file?
> Must be something wrong in the Swagger annotations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1908) Modular Security Architecture
[
https://issues.apache.org/jira/browse/FINERACT-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1908:
---
Fix Version/s: (was: 1.10.0)
> Modular Security Architecture
> -
>
> Key: FINERACT-1908
> URL: https://issues.apache.org/jira/browse/FINERACT-1908
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Aleksandar Vidakovic
>Assignee: Aleksandar Vidakovic
>Priority: Major
> Labels: FIPS
> Fix For: 1.11.0
>
> Attachments: FIPS-0001.pdf, image (9).png
>
>
> Background and Motivation
>
> Our current security architecture is based on a example in Spring Security’s
> documentation and implemented on top of JDBC. For a long time we’ve only
> supported basic authentication which was later complemented with a homegrown
> OAuth implementation and another module for one time passwords. On the
> authorization side we support a straight forward RBAC (role based access
> control) model again implemented on top of JDBC. This approach worked for
> quite a while, but end users and integrators wish a more flexible solution.
> Effectively, we are forcing users to adapt to our current security model. In
> most cases they have already existing security infrastructure (e.g.
> ActiveDirectory/LDAP for user info storage and role assignments) and would
> like to integrate Fineract with it. And last, in some more advanced and more
> complex setups the role/permission based access concept might not be
> sufficient for authorization; sometimes additional information (external to
> Fineract) might be needed for additional evaluation. The current setup makes
> it at the least very hard (if not impossible) to achieve these goals.
>
> h2. Target Personas
>
> * integrators
> * end users
> * BaaS
>
> h2. Goals
>
> * separate the current security infrastructure as much as possible from
> Fineract’s core; i. e. make it a custom module
> * create the OAuth Client aka Keycloak module as a drop-in replacement for
> the current security mechanics
> * delegate everything authentication/authorization related to 3rd party
> libs/frameworks/products/services
> * re-use 3rd party libs/frameworks/products/services user interfaces and
> remove corresponding views (e. g. user management) from Fineract web app
> * as minimal refactoring as possible in the short/mid term
> * keep backwards compatibility for a couple of major releases
> * provide good documentation and/or automated tools for migration
>
> h2. Non-Goals
>
> * Fineract as a standalone identity server
>
> h2. Proposed API Changes
>
> h3. AppUser
>
> Unfortunately this class is both JPA entity class and implements Spring
> Security’s "User" interface. The current dependencies and usage in code is
> not ideal (at least when it’s business logic), but the main challenge is that
> the database table behind this JPA entity is related pretty much all over the
> place via joins.
>
> h3. PlatformUserDetailsService
>
> Ideally this service should not be used directly anymore in Fineract’s core.
>
> h3. OAuth Client Auto Configuration
>
> After years of having multiple competing OAuth packages Spring consolidated
> their efforts in two libraries:
>
> {color:#00}implementation
> "org.springframework.boot:spring-boot-starter-oauth2-client"{color}
> {{implementation
> "org.springframework.boot:spring-boot-starter-oauth2-resource-server"}}
>
> Especially the Keycloak configuration is very easy (3 lines in
> application.properties).
>
> h3. BCrypt Support Module for Keycloak
>
> Unfortunately Keycloak doesn’t support BCrypt hashing for passwords out of
> the box, but BCrypt is widely used in Spring Boot applications and the
> default for Fineract. It’s very easy to create an extension module for
> Keycloak to supprot BCrypt too; that way we can migrate existing user
> accounts out of Fineract’s database tables without forcing everyone to reset
> their passwords. Not a strict technical requirement, but helps to smooth the
> transition.
>
> h3. Open Policy Agent integration
>
> To my knowledge there is no official Spring Security module/support for Open
> Policy Agent. Doesn’t really matter that much, because the communication with
> the OPA server is pretty much handled via one endpoint (again, for Java there
> is no official client, but the implementation is easy). Enforcing the OPA
> rules happens then with a Spring Security Voter. Some more thought needs to
> go into what information we send to OPA. At the least we would need:
> * user name
> * authorities/roles
> * service name and function name that is being executed
> * optional: parameters that are passed to the function
> It should be possible to intercept these calls with minimal coding effo
[jira] [Updated] (FINERACT-1315) transfer of client from one office to another are not posting accounting entries
[ https://issues.apache.org/jira/browse/FINERACT-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1315: --- Fix Version/s: (was: 1.10.0) > transfer of client from one office to another are not posting accounting > entries > > > Key: FINERACT-1315 > URL: https://issues.apache.org/jira/browse/FINERACT-1315 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Client >Affects Versions: 1.4.0 >Reporter: Bharath Gowda >Assignee: Nayan Ambali >Priority: Blocker > Fix For: 1.11.0 > > Attachments: 1.png, 2.png > > > The transactions at the loan level which happens when we transfer a client > from one office to another are not posting accounting JE entries. > > to reproduce > 1. create/disburse an individual loan with any loan product that has > accounting enabled > 2. transfer the client from one office to another office using the "transfer > client" button from the client view screen > 3. active loans will get "transfer initiated" and "transfer approved" > transactions which will actually transfer the loan's portfolio to a new > transferred branch, which is not happening currently. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2044) Fix launch configuration for Spring 3.2.x
[ https://issues.apache.org/jira/browse/FINERACT-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2044: --- Fix Version/s: (was: 1.10.0) > Fix launch configuration for Spring 3.2.x > - > > Key: FINERACT-2044 > URL: https://issues.apache.org/jira/browse/FINERACT-2044 > Project: Apache Fineract > Issue Type: Bug >Reporter: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1485) New Loan Charge type "upfront disbursement fees"
[ https://issues.apache.org/jira/browse/FINERACT-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1485: --- Fix Version/s: (was: 1.10.0) > New Loan Charge type "upfront disbursement fees" > > > Key: FINERACT-1485 > URL: https://issues.apache.org/jira/browse/FINERACT-1485 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.8.0 >Reporter: Bharath Gowda >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.11.0 > > Attachments: Upfront fee requirement.xlsx, screenshot-1.png > > > Refer Attachment for full details of the requirement. > |Requirement|Changes | > |New loan entity - fee type to be introduced |Upfront Disbursement Fee| > | > Upfront fee can be on |1. % approved amount > 2. Flat| > |Actual Disbursement Amount =|Disbursement amount entered - upfront fees > amount| > |Repayment schedule|Repayment schedule should be calculated based on the > actual disbursement amount(Disbursement amount entered - upfront fees)| > |Transaction|Upfront fees should be collected at the time of disbursement(as > shown in the transaction sample)| > |Accounting entry|no changes in accounting entries. it remains standard OOB > for disbursement, fees, and transactions| > |Repayment schedule calculation |once disbursed with the actual > disbursement amount- all calculation remains the same as OOB as per > product configuration| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2070) Integrate the new test framework into the public build pipeline
[ https://issues.apache.org/jira/browse/FINERACT-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2070: --- Fix Version/s: (was: 1.10.0) > Integrate the new test framework into the public build pipeline > --- > > Key: FINERACT-2070 > URL: https://issues.apache.org/jira/browse/FINERACT-2070 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2075) Introduce Lombok to the loanproduct module
[
https://issues.apache.org/jira/browse/FINERACT-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-2075:
---
Fix Version/s: (was: 1.10.0)
> Introduce Lombok to the loanproduct module
> --
>
> Key: FINERACT-2075
> URL: https://issues.apache.org/jira/browse/FINERACT-2075
> Project: Apache Fineract
> Issue Type: Sub-task
>Reporter: Zeyad Nasef
>Priority: Minor
> Fix For: 1.11.0
>
>
> Refactor the classes under the {{loanproduct}} package by introducing some
> lombok annotations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1977) 4-eye-principle not working for any maker-checker permission
[ https://issues.apache.org/jira/browse/FINERACT-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1977: --- Fix Version/s: (was: 1.10.0) > 4-eye-principle not working for any maker-checker permission > > > Key: FINERACT-1977 > URL: https://issues.apache.org/jira/browse/FINERACT-1977 > Project: Apache Fineract > Issue Type: Bug > Components: Security >Affects Versions: 1.9.0 >Reporter: Peter Santa >Priority: Critical > Labels: BeanSalad > Fix For: 1.11.0 > > > h1. Steps to reproduce > * Set up a permission with maker flag > * Set up a corresponding permission with checker flag > h1. Expected result > * When performing the maker action the processing stops and waits for > checking > * On checking, the action gets performed > h1. Real result > All actions get performed without checking -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1760) Manage external IDs
[
https://issues.apache.org/jira/browse/FINERACT-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1760:
---
Fix Version/s: (was: 1.10.0)
> Manage external IDs
>
>
> Key: FINERACT-1760
> URL: https://issues.apache.org/jira/browse/FINERACT-1760
> Project: Apache Fineract
> Issue Type: New Feature
>Reporter: Mihaly Dallos
>Assignee: Adam Saghy
>Priority: Major
> Labels: PepperSoup
> Fix For: 1.11.0
>
>
> h1. Introduction
> Transactions may change due to correction. Correction can be done by
> reverting a transaction. This can lead to removing and adding transactions
> back to an account. It results new ID distribution from the transaction
> sequence. External systems may not want to follow up on these changes but
> rather access transactions as they are at their end state. In order to be
> able to direct client immediately to the right record an additional
> identifier is to be used.
> Supporting externalId is a long time wanted functionality with two major
> benefits:
> * Not an auto incremented number (privacy, harder to guess)
> * Not represent any internal state
> h2. Requirements
> * 🟩 Supporting external id for identifying and fetching some if the entities
> in Fineract
> * 🟩 API enhancement to support targeting by external id
> * ✅ External id can be provided in API request
> * 🟩 Extend API response with external id
> * 🟩 Support external id auto generation (configurable)
> *+External identifier+*
> * Must be unique
> * Immutable
> * Customer (Caller) provided
> * Ability to generate automatically (configurable)
> h3. *+Database+*
> External identifier field to be stored in the loan table
> {+}type{+}: String
> {+}indexing{+}: true
> h3. +Configuration+
> Enable to auto generate external id (if not provided).
> By default it should be disabled.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1988) Modular Security Architecture: Phase 5
[ https://issues.apache.org/jira/browse/FINERACT-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1988: --- Fix Version/s: (was: 1.10.0) > Modular Security Architecture: Phase 5 > -- > > Key: FINERACT-1988 > URL: https://issues.apache.org/jira/browse/FINERACT-1988 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > Add Open Policy Agent based authorization module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2025) SQL Query Improvement
[ https://issues.apache.org/jira/browse/FINERACT-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2025: --- Fix Version/s: (was: 1.10.0) > SQL Query Improvement > - > > Key: FINERACT-2025 > URL: https://issues.apache.org/jira/browse/FINERACT-2025 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.8.4 >Reporter: Ed Cable >Assignee: Mihaly Dallos >Priority: Major > Fix For: 1.11.0 > > > Multiple areas within fineract-provider to be improved. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1948) Loan repayment by account transfer transaction type should not be withdrawal
[ https://issues.apache.org/jira/browse/FINERACT-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1948: --- Fix Version/s: (was: 1.10.0) > Loan repayment by account transfer transaction type should not be withdrawal > > > Key: FINERACT-1948 > URL: https://issues.apache.org/jira/browse/FINERACT-1948 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.7.2, 1.7.0, 1.8.3, 1.8.2, 1.8.1 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.11.0 > > Attachments: image-2023-07-31-23-11-05-824.png > > > When a user transfers money from a savings account to pay off a loan, the > transaction type is tagged as a withdrawal yet this is a loan repayment. The > transaction type should be adjusted to suit the transaction as it gets handy > for repayments with standing instructions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1001) Enable and Enforce PMD on Fineract
[ https://issues.apache.org/jira/browse/FINERACT-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1001: --- Fix Version/s: (was: 1.10.0) > Enable and Enforce PMD on Fineract > -- > > Key: FINERACT-1001 > URL: https://issues.apache.org/jira/browse/FINERACT-1001 > Project: Apache Fineract > Issue Type: Sub-task >Affects Versions: 1.8.0 >Reporter: Awasum Yannick >Priority: Minor > Fix For: 1.11.0 > > Attachments: main.html > > > Enable and Enforce PMD ( [https://pmd.github.io/ )|https://pmd.github.io/] on > Fineract. Make PMD fail until violations are fixed just like we do for > Spotbug, checkstyle etc. See previous work here: > [https://github.com/apache/fineract/pull/295] > See where PMD was commented out because it was not use: > [https://github.com/apache/fineract/pull/612] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2027) Permission evaluation for jobs
[ https://issues.apache.org/jira/browse/FINERACT-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2027: --- Fix Version/s: (was: 1.10.0) > Permission evaluation for jobs > -- > > Key: FINERACT-2027 > URL: https://issues.apache.org/jira/browse/FINERACT-2027 > Project: Apache Fineract > Issue Type: Improvement > Components: Job Scheduler >Affects Versions: 1.8.4 >Reporter: Peter Santa >Priority: Major > Labels: BeanSalad > Fix For: 1.11.0 > > > h1. Background > Currently, when a job gets triggered via API, the permission of the > authenticated user is evaluated, whether it has permission to run jobs, > generally. If yes, the initiator user gets replaced by System user in the > context, and the job’s actions get triggered using that context. There are no > further permission checking while running jobs, e.g. for the specific job, or > a step of the job. > Whenever any permission checking gets introduced, during running the job, > performing actions will not be permitted, because by default the used System > user does not have any permission - this could break currently running, live > systems. > h1. Goal > Have the permissions evaluated based on the authenticated user and the > action, when triggering a job via API. Have job-specific permission. > h1. Analysis > * to be evaluated, whether it worked like this earlier, or got broken when > implementing features recently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1702) Status of submitted applications for approval or processing
[ https://issues.apache.org/jira/browse/FINERACT-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1702: --- Fix Version/s: (was: 1.10.0) > Status of submitted applications for approval or processing > --- > > Key: FINERACT-1702 > URL: https://issues.apache.org/jira/browse/FINERACT-1702 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Affects Versions: 1.7.0 >Reporter: ibrahim kimbugwe >Priority: Major > Fix For: 1.11.0 > > > Upon submitting a loan application GL entry or any other task that requires > approval in a maker checker-controlled working environment, It is very > important to have a window to monitor the status of the submission even if I > don't have the rights to approve. > This goes a long way to help in the follow-up and management of tasks. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1918) Create Loan Product - field transactionProcessingStrategyCode is breaking Mifos-UI
[
https://issues.apache.org/jira/browse/FINERACT-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-1918:
---
Fix Version/s: (was: 1.10.0)
> Create Loan Product - field transactionProcessingStrategyCode is breaking
> Mifos-UI
> --
>
> Key: FINERACT-1918
> URL: https://issues.apache.org/jira/browse/FINERACT-1918
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Affects Versions: 1.9.0
>Reporter: Mohit Sinha
>Priority: Major
> Fix For: 1.11.0
>
> Attachments: Screenshot 2023-04-06 at 3.04.35 PM.png, Screenshot
> 2023-04-06 at 3.05.08 PM.png, Screenshot 2023-04-06 at 3.05.27 PM.png
>
>
> Till version {_}1.8.4{_}, the API {_}api/v1/loanproducts{_}, was having the
> field {_}transactionProcessingStrategyId{_}.
> I have verified that the functionality works fine till {_}1.8.4{_}.
> This field is currently handled in the develop branch of openmf/community-app.
> In the current _develop_ branch of Fineract,
> _transactionProcessingStrategyCode_ is expected in place of it.
> So, this is causing a breaking change in the community-app.
> Should we fix it over here by allowing both these fields and giving more
> precedence to _transactionProcessingStrategyId_ if both the fields are passed.
> Or should a commit be made in the community-app to fix this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1670) Introduce Auditable entities - Storing date time in UTC
[ https://issues.apache.org/jira/browse/FINERACT-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1670: --- Fix Version/s: (was: 1.10.0) > Introduce Auditable entities - Storing date time in UTC > --- > > Key: FINERACT-1670 > URL: https://issues.apache.org/jira/browse/FINERACT-1670 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.7.0, 1.8.0 >Reporter: Adam Saghy >Assignee: Adam Saghy >Priority: Major > Fix For: 1.11.0 > > Attachments: Re_ Timezone issues with Daylight savings.rtfd.zip > > > AbstractAuditableCustom interface to be used more widely with entities. > Many Fineract entity has no proper audit fields (creation date & time, last > modification date & time, created by, modified by entries. > Many entities has a variety of the above fields but with custom > implementation and not fit perfectly for audit purposes (see LoanTransaction). > All business entity ( utility entities excluded) should implement the above > interface and fill properly the audit fields with a common, generic way. > The similar custom fields to be removed / repurposed. > The Datetime fields to be stored in UTC! The datetime fields when its fetched > from the DB it is UTC, so it needs to be converted to the proper tenant > timezone if there is any business logic attached to them. > > Storing in UTC is important to avoid daylight savings and "incorrect timezone > is used" issues: > - Some places the tenant timezone used > - Som places the system timezone used > > *Acceptance criteria* > * Every custom fields with similar purpose to be decommissioned > * All datetime field to be utc > * It must be a backward-compatible change! > ** Column cannot be removed! > *Change proposal* > * created_on_utc: Timezone aware datetime field > * last_modified_on_utc: Timezone aware datetime field > * created_by: Long (AppUser id) > * last_modified_by: Lond (AppUser id) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2021) Type-safe REST API layer
[ https://issues.apache.org/jira/browse/FINERACT-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2021: --- Fix Version/s: (was: 1.10.0) > Type-safe REST API layer > > > Key: FINERACT-2021 > URL: https://issues.apache.org/jira/browse/FINERACT-2021 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Priority: Major > Labels: FIPS > Fix For: 1.11.0 > > > h2. Background and Motivation > Fineract initial planning and code architecture predates some of the > frameworks and current best practices. That and the fact that we have some > not so easy to parse data structures led to the decision to use Google's GSON > library and parse incoming API requests manually and to capture all request > bodies in String variables. The downside of doing this decision are: > * by capturing all incoming request bodies in Strings we lose all type > information > * we need to manually reintroduce types by creating dummy classes that are > solely there to create an OpenAPI descriptor > * it is easy to introduce bugs while refactoring, because non of the > refactoring tools in any of the IDEs can help > * we have to maintain a lot of "magic" Strings to poke into the JSON data > structures (again, no type-safety) > * we have a lot of boilerplate code for manual JSON parsing that we have to > maintain (rough estimate 10-15% of the entire code base) > * because the JSON parsing is so tedious and time consuming a couple of > developers decided to skip the layered architecture rules; and with that they > tied the REST API layer to the business logic/service layer (not a good > practice); the business logic should not contain any information about how > and in which format we exchange API requests > h2. Target Personas > * developers > * integrators > * BaaS > h2. Goals > * migrate current JAX-RS REST resource classes to Spring's Web MVC > * use Spring Boot's first class integration of Jackson for JSON parsing > * get rid of entire manual JSON code base (including the use of GSON) > * handle difficult/non-standard data structures with Jackson Serializer and > Deserializer implementations > * all incoming and outgoing API requests need to be mapped to proper Java > classes in packages "data" > * all business logic services need to have "data" classes as input and > output parameters > * remove all JSON related input and output parameters from business logic > services > * remove all dummy/helper classes related to OpenAPI descriptor generation > * clear separation between data and domain/entity classes > * domain classes should be only used internal to respective business logic > service and not leak outside of its package/feature/module > * use MapStruct ([https://mapstruct.org/)] to generate as much mapping code > as possible without manual intervention (mappers should only be used internal > to business logic services) > * use validation annotations on data classes to delegate as much as possible > to Java validation framework instead of doing our own boilerplate > "if-then-else" code > * keep REST API backwards compatibility with version 1.9.0 > h2. Non-Goals > * change/improve REST API structure > * move all current RESTeasy based integration tests to Spring MVC's JUnit > test support (separate project/pull request/ticket) > h2. Proposed API Changes > h3. JAX-RS REST resource classes > Move all JAX-RS REST resource classes to Spring Web MVC controllers (with all > annotations etc.). It might be possible to use OpenRewrite to automate part > of this work (there is a module for refactoring JAX-RS to Spring Web MVC. > This allows us to take advantage of first class support for JUnit like > testing in Spring (replacing our unmaintainable integration tests... which > lack themselves type safety). > h3. REST controller input and output parameters > Make sure all endpoint receive and generate type safe data. All input/output > parameter related data structures should reside in "data" packages. > h3. Business logic services > All input and output parameters in the business logic layer need to be mapped > to "data" classes. Internal domain/entity classes should not leak outside of > the business logic classes. > h3. Data/DTO to domain/entity mapping > All mapping between data and domain classes should be mapped with MapStruct. > The developers only have to provide annotations (if necessary) and automate > the mapping code generation with MapStruct. > h2. Risks > Migrating from JAX-RS to Spring Web MVC and re-introduce type-safety will be > an ongoing effort over a couple of weeks/months. During that time we'll have > 2 different frameworks handling the API requests. There might be subtle > changes in the behavior. > h2. ETA
[jira] [Updated] (FINERACT-1397) Interest calculation issue when repayment is made on the disbursement day
[ https://issues.apache.org/jira/browse/FINERACT-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1397: --- Fix Version/s: (was: 1.10.0) > Interest calculation issue when repayment is made on the disbursement day > - > > Key: FINERACT-1397 > URL: https://issues.apache.org/jira/browse/FINERACT-1397 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: Bharath Gowda >Assignee: Avik Ganguly >Priority: Major > Fix For: 1.11.0 > > Attachments: interest calculation issue.xlsx, product > configuration.png > > > Interest calculation is wrong when repayment is made on the disbursement day > for the daily interest loan product > > To reproduce the issue > 1. Create a loan product with daily interest calculation and interest > recalculation enabled.(have attached the screenshot of the loan product > configuration) > 2. Create/approve/disburse a loan account with a first repayment date of 30 > days gap from the disbursement date. > 3. Make the repayment on the same day of the disbursement date and verify the > interest > > check excel calculation for example issue and expected result. > > Any other date apart from the disbursement date repayment the interest > calculation is happening currently. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1560) Enhance Retrieve loan information by Client ID API for new required response parameters
[ https://issues.apache.org/jira/browse/FINERACT-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1560: --- Fix Version/s: (was: 1.10.0) > Enhance Retrieve loan information by Client ID API for new required response > parameters > --- > > Key: FINERACT-1560 > URL: https://issues.apache.org/jira/browse/FINERACT-1560 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.6.0, 1.7.0, 1.8.0 >Reporter: Ed Cable >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.11.0 > > > For retrieving the loan information for a client, we need to enhance the > following API with additonal parameters outlined below. > +GET:+ > _https://DomainName/api/v1/loans/template?templateType=individual&clientId=1&productId=1_ > > |New Parameter|Value/Amount| > |available_disbursement_amount|It is the difference of approved amount and > disbursed amount| > |past_due_days|No of days the loan is overdue,current date - duedate| > |next_payment_due_date|Based on the current date, need to populate the next > payment due date| > |delinquent_days|No of days the loan is in arrears, current date - > duedate-grace period| > |delinquent_date|Date the loan is in arrears, current date - duedate-grace > period| > |delinquent_amount|amount overdue after the grace period| > |last_payment_date|last repayment made date on the loan| > |last_payment_amount|last repayment amount made date on the loan| > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1577) TLS support in fully managed serverless environments
[ https://issues.apache.org/jira/browse/FINERACT-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1577: --- Fix Version/s: (was: 1.10.0) > TLS support in fully managed serverless environments > > > Key: FINERACT-1577 > URL: https://issues.apache.org/jira/browse/FINERACT-1577 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2079) Rectify query for cashier transactions
[ https://issues.apache.org/jira/browse/FINERACT-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-2079: --- Fix Version/s: (was: 1.10.0) > Rectify query for cashier transactions > -- > > Key: FINERACT-2079 > URL: https://issues.apache.org/jira/browse/FINERACT-2079 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.9.0 >Reporter: Kigenyi Wilfred >Priority: Major > Labels: easyfix > Fix For: 1.11.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > The query for cashier transactions in > TellerManagementReadPlatformServiceImpl.retrieveCashierTransactionsWithSummary > references an non-existent column appuser_id on the savings transaction > table which leads causes an exception -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1792) Update OAuth configuration and provide sample Keycloak setup
[ https://issues.apache.org/jira/browse/FINERACT-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dailey updated FINERACT-1792: --- Fix Version/s: (was: 1.10.0) > Update OAuth configuration and provide sample Keycloak setup > > > Key: FINERACT-1792 > URL: https://issues.apache.org/jira/browse/FINERACT-1792 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.11.0 > > > Do not use the Keycloak Spring Boot adapter, because it will be deprecated > soon. Use the officially preferred Spring OAuth client auto configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2003) Enforce change of password on first logon
[
https://issues.apache.org/jira/browse/FINERACT-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-2003:
---
Fix Version/s: (was: 1.10.0)
> Enforce change of password on first logon
> -
>
> Key: FINERACT-2003
> URL: https://issues.apache.org/jira/browse/FINERACT-2003
> Project: Apache Fineract
> Issue Type: New Feature
>Reporter: John Ruhiu
>Priority: Major
> Fix For: 1.11.0
>
>
> Add the ability to force the user to reset their password on the first logon
> and when a password has been reset by admin or using forgot password feature.
> If its the first time the user is login in, the system should ask them to
> reset the password and send them to the password reset page where they will
> enter a new password(and repeat).
> The system will process the request and redirect them to the login page where
> they will enter the new password to gain access.
> Note: the password reset feature already exists under user/profile/change
> password on the mifos UI
>
> {*}ASSUMPTIONS{*}:
> 1. Email is configured in fineract (SMTP config) Admin>System>External
> Services>External Services (Email Config)
> That means the email is working (when a new user is created, an email with
> attached sample is sent to the user).
>
> 2. Password validation already exists (Admin>Organisation>Password preference)
> 3. Endpoint for password change already exists
> 4. We are not sending deep link nor generating a link for the user to change
> to change their password. We are assuming the user has received their
> credentials and they know the fineract / mifos link from which they can login.
>
> *WHAT WE NEED TO DO:*
> # Add to global configuration an option to allow first login password change
> # On logon detect if the global configuration for first login password
> change is enabled. If True then detect whether the user is logging in for the
> first time. If true force the user to change their password.
> # On the screen for password change only allow them to enter new password
> and repeat. Ensure the password complies with the password policies (see
> assumption No.2).
> # After successful change of password redirect the user to login password to
> allow them login.
> *OUT SCOPE:*
> # Multifactor authentication.
> {{}}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
