[jira] [Updated] (FINERACT-626) MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01
[ https://issues.apache.org/jira/browse/FINERACT-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-626: -- Fix Version/s: (was: 1.9.0) > MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01 > -- > > Key: FINERACT-626 > URL: https://issues.apache.org/jira/browse/FINERACT-626 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System >Affects Versions: 1.8.0 >Reporter: Jimmy Jubha Mayala >Priority: Major > Labels: gsoc, p2 > Fix For: 3.0.0 > > > We need a feature in Fineract to enhance cash distribution from head office > to branches, for examplE, in our office we have taken a loan from bank and we > want it be distributed into our branches, we are able to inject this loan > into Head office accounts, but how is it going to be sent to branches > accounts? this is where we got stuck since mifos x 17.07.01 we are using does > not have this feature. > We do request any developer to pick this task. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-633) New Penalty Charge not appearing in Product dropdown list
[ https://issues.apache.org/jira/browse/FINERACT-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-633: -- Fix Version/s: (was: 1.9.0) > New Penalty Charge not appearing in Product dropdown list > - > > Key: FINERACT-633 > URL: https://issues.apache.org/jira/browse/FINERACT-633 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.8.0 > Environment: v18.03.01 >Reporter: Sifiso Mtetwa >Priority: Minor > Labels: GSOC, Volunteer, easyfix, p1 > Fix For: 3.0.0 > > > We have been developing a new feature for penalties overdue on maturity > [https://mifosforge.jira.com/browse/MIFOSX-2848?filter=-2] We have an issue > where after you create the penalty in the charges area with a new charge time > type of overdue on maturity and submit it, it does not appear in loan > products penalties dropdown box for selection. Wanted to find out which class > fetches the penalties that are fetched to appear in this list yet in table > m_charges it appears fine. We have added some code in the UI to fetch the > required variables but it still does not appear. We can’t proceed beyond this > point. Please advise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-694: -- Fix Version/s: (was: 1.9.0) > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.8.0 >Reporter: Saksham Handu >Priority: Major > Fix For: 3.0.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-463) Dashboard showing no data for 'Amount Collected for Today' even though there are transactions today
[ https://issues.apache.org/jira/browse/FINERACT-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-463: -- Fix Version/s: (was: 1.9.0) > Dashboard showing no data for 'Amount Collected for Today' even though there > are transactions today > - > > Key: FINERACT-463 > URL: https://issues.apache.org/jira/browse/FINERACT-463 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, community-app, p1, > verify > Fix For: 3.0.0 > > Attachments: dashboard.png > > > Reported by Onyedikachi Nwosu > 1. Create a new office and create a client under the new office. > 2. perform a deposit of 10,000 to a savings account and issued a loan to the > value of 10,000 for the same client. > As can be seen from the attached screenshot, On the dashboard, Amount > Disbursed for Today reflects the 10,000 loan, but the Amount Collected for > Today does not reflect 10,000 savings made. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-676) Address issue with creating rejected data table at savings account level
[ https://issues.apache.org/jira/browse/FINERACT-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-676: -- Fix Version/s: (was: 1.9.0) > Address issue with creating rejected data table at savings account level > - > > Key: FINERACT-676 > URL: https://issues.apache.org/jira/browse/FINERACT-676 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-471) Preview feature for uploaded document
[ https://issues.apache.org/jira/browse/FINERACT-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-471: -- Fix Version/s: (was: 1.9.0) > Preview feature for uploaded document > - > > Key: FINERACT-471 > URL: https://issues.apache.org/jira/browse/FINERACT-471 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, System >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > Fix For: 3.0.0 > > > Enhance Request by Boniphace Fredrick > Original Description: > Currently the system allows to upload a document and once you want to view it > again there is only one option ie, to download it. > This act can probably violate client's privacy( ie, client information > vulnerability) for example if a user(eg. Loan officer) uses somebody computer > to access system, so there is possibility he/she can download a document and > forget to delete if from that local machine > Therefore I suggest there should first an option to preview the document fist > maybe as a pdf and then a user can choose either to download, print or just > view it only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-674) Address issue with creating rejected data table at loan account level
[ https://issues.apache.org/jira/browse/FINERACT-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-674: -- Fix Version/s: (was: 1.9.0) > Address issue with creating rejected data table at loan account level > -- > > Key: FINERACT-674 > URL: https://issues.apache.org/jira/browse/FINERACT-674 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-670) Transaction 'Notes' should be displayed in summary of transaction
[ https://issues.apache.org/jira/browse/FINERACT-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-670: -- Fix Version/s: (was: 1.9.0) > Transaction 'Notes' should be displayed in summary of transaction > - > > Key: FINERACT-670 > URL: https://issues.apache.org/jira/browse/FINERACT-670 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: GSOC, Volunteer, gci, p1 > Fix For: 3.0.0 > > > Whenever we make Transactions like Loan Repayments, we can capture Notes. But > currently, after transaction is done ,these notes can be seen in Loan > Account tab rather than in Transaction Details. This makes it difficult to > determine which transaction the note applied to. > Expected: Notes should be shown in Transaction details page. Likewise, this > notes field should be part of the fields that would get displayed in a > transaction details report. -- 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
]
Aleksandar Vidakovic updated FINERACT-1984:
---
Fix Version/s: 1.10.0
(was: 1.9.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.10.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-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 ] Aleksandar Vidakovic updated FINERACT-1940: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.0 > > -- 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 ] Aleksandar Vidakovic updated FINERACT-1792: --- Fix Version/s: (was: 1.9.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 > > 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-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 ] Aleksandar Vidakovic updated FINERACT-1792: --- Fix Version/s: 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.10.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] [Resolved] (FINERACT-1727) Introduce Lombok to accountnumberformat module
[ https://issues.apache.org/jira/browse/FINERACT-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1727. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to accountnumberformat module > -- > > Key: FINERACT-1727 > URL: https://issues.apache.org/jira/browse/FINERACT-1727 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in accountnumberformat module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1776) Introduce Lombok to office module
[ https://issues.apache.org/jira/browse/FINERACT-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1776. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to office module > - > > Key: FINERACT-1776 > URL: https://issues.apache.org/jira/browse/FINERACT-1776 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in office module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1779) Introduce Lombok to teller module
[ https://issues.apache.org/jira/browse/FINERACT-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1779. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to teller module > - > > Key: FINERACT-1779 > URL: https://issues.apache.org/jira/browse/FINERACT-1779 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in teller module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1715) Introduce Lombok to cob module
[ https://issues.apache.org/jira/browse/FINERACT-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1715. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to cob module > -- > > Key: FINERACT-1715 > URL: https://issues.apache.org/jira/browse/FINERACT-1715 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in cob module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1780) Introduce Lombok to workingdays module
[ https://issues.apache.org/jira/browse/FINERACT-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1780. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to workingdays module > -- > > Key: FINERACT-1780 > URL: https://issues.apache.org/jira/browse/FINERACT-1780 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in workingdays module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1743) Introduce Lombok to documentmanagement module
[ https://issues.apache.org/jira/browse/FINERACT-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1743. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to documentmanagement module > - > > Key: FINERACT-1743 > URL: https://issues.apache.org/jira/browse/FINERACT-1743 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in documentmanagement module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1732) Introduce Lombok to bulkimport module
[ https://issues.apache.org/jira/browse/FINERACT-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1732. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to bulkimport module > - > > Key: FINERACT-1732 > URL: https://issues.apache.org/jira/browse/FINERACT-1732 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in bulkimport module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1742) Introduce Lombok to dataqueries module
[ https://issues.apache.org/jira/browse/FINERACT-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1742. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to dataqueries module > -- > > Key: FINERACT-1742 > URL: https://issues.apache.org/jira/browse/FINERACT-1742 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in dataqueries module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- 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
]
Aleksandar Vidakovic updated FINERACT-1908:
---
Fix Version/s: 1.10.0
(was: 1.9.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.10.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
[jira] [Updated] (FINERACT-2005) Prohibit password re-use
[ https://issues.apache.org/jira/browse/FINERACT-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-2005: --- Fix Version/s: 1.10.0 (was: 1.9.0) > Prohibit password re-use > > > Key: FINERACT-2005 > URL: https://issues.apache.org/jira/browse/FINERACT-2005 > Project: Apache Fineract > Issue Type: New Feature >Reporter: John Ruhiu >Priority: Major > Fix For: 1.10.0 > > > A user should not reuse the same password. > Add the ability to check if the password entered by the user when resetting > their password or when the system admin is resetting the user password has > ever been used by the same user before. If so, reject with a message telling > the user to enter a different password. > Allow admin to set the max number of passwords the system will check when > evaluating pass re-use i.e the system should for example allow a user to use > the same password, if 5 other passwords have been used. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-2000) Clean-up retryable error codes
[
https://issues.apache.org/jira/browse/FINERACT-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-2000:
---
Fix Version/s: 1.10.0
(was: 1.9.0)
> Clean-up retryable error codes
> --
>
> Key: FINERACT-2000
> URL: https://issues.apache.org/jira/browse/FINERACT-2000
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Performance, Savings
>Affects Versions: 1.9.0
>Reporter: Peter Santa
>Priority: Major
> Labels: BeanSalad
> Fix For: 1.10.0
>
>
> Current Fineract behaviour:
> * optimistic locking exception: 423 {{SC_LOCKED}}
> the request was retried inside Fineract (configuration times) but was not
> successful
> *
> ** status: FAILED
> *
> ** when: more than one thread is trying to modify the same entity
> concurrently
> *
> ** caller: should retry with a NEW idempotency key
> *
> ** ams connector: implemented retry configuration times
> *
> ** issue: not ideal as 423 is a WebDav code
> *
> ** suggested: change to return code to 409 {{SC_CONFLICT}}
> * pessimistic locking: 409 {{SC_CONFLICT}}
> the request was retried inside Fineract (different configuration times) but
> was not successful
> *
> ** status: not registered currently, should be FAILED
> *
> ** when: the COB process is currently running and we try to modify the entity
> only implemented on Loan so we will not have it on SavingsAccount
> *
> ** caller: should retry with a NEW idempotency key
> *
> ** ams connector: no retry, currently returns null
> *
> ** issue: same code as process in progress, must be different - already on
> prod, so finer act community should allow the change
> *
> ** suggested: fix audit log and keep return code 409 {{SC_CONFLICT}}
> * process in progress: 409 {{SC_CONFLICT}}
> the request was already started by a different thread
> *
> ** status: IN PROGRESS
> *
> ** when: the process with same idempotency key was already started by a
> different thread
> specially for jobs (async requests), or for other processes if more than one
> instance can send the same request simultaneously (probably can not happen)
> *
> ** caller: should retry with the SAME idempotency key
> *
> ** ams connector: no retry, currently returns null because we do not have
> async requests, so another instance should return the correct response
> (success or failed)
> *
> ** issue: same code as pessimistic locking, must be different - already on
> prod, so finer act community should allow the change
> *
> ** suggested: change return code to 425 {{Too Early (RFC 8470), return null
> is probably ok}}
> * deadlock: 500 (not handled so maybe different)
> deadlock is automatically retried but takes significant time so better to
> avoid
> *
> ** status: FAILED
> *
> ** when: example: two batches perform operation on the same entities but in
> different order
> *
> ** caller: should retry with a NEW idempotency key
> *
> ** ams connector: not handled
> *
> ** issue: implement or better to change the logic
> one of the deadlock types we already fixed in the ams connector:
> batch1: account1 operation, account2 operation; batch2: account2 operation,
> account1 operation
> was changed to
> batch1: account1 operation, account2 operation; batch2: account1 operation,
> account2 operation
> we also encountered deadlock on Savings transactions which is not handled yet
> *
> ** suggested: change Savings Transaction handling (core change) and handle
> deadlock exception
> change return code to 409 {{SC_CONFLICT}}
--
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 ] Aleksandar Vidakovic updated FINERACT-1956: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.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-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
]
Aleksandar Vidakovic updated FINERACT-2003:
---
Fix Version/s: 1.10.0
(was: 1.9.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.10.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)
[jira] [Updated] (FINERACT-2004) Limit login re-tries
[ https://issues.apache.org/jira/browse/FINERACT-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-2004: --- Fix Version/s: 1.10.0 (was: 1.9.0) > Limit login re-tries > > > Key: FINERACT-2004 > URL: https://issues.apache.org/jira/browse/FINERACT-2004 > Project: Apache Fineract > Issue Type: New Feature >Reporter: John Ruhiu >Priority: Major > Fix For: 1.10.0 > > > Limit the number of login attempts to N times where N is a configurable value > under system/configurations. > To do: > # Add ability to set maximum login retries as a global configuration > # Check maximum login times and lock account if exceeded > Notes: > * The global configuration should allow user to turn it on/off > * The global configuration should allow user to set maximum retries value > * Failed logins will set the failed login attempts value and increase it by > 1 until max retries have been reached as set in the global configuration > * Successful login resets the failed login attempts to zero. For example, a > user has tried and failed to login 2 times but succeeds on the third. On this > third attempt, the failed login value is set to zero. > * Add this to permissions list to allow granting the same to qualified roles > * Add tests to allow test automation > * Add documentation to allow autogeneration by swagger docs -- 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 ] Aleksandar Vidakovic updated FINERACT-1983: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.0 > > > h1. Goal > Separate date handling of savings and loan accounts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1718) Introduce Lombok to interoperation module
[ https://issues.apache.org/jira/browse/FINERACT-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1718. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to interoperation module > - > > Key: FINERACT-1718 > URL: https://issues.apache.org/jira/browse/FINERACT-1718 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in interoperation module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1740) Introduce Lombok to core module
[ https://issues.apache.org/jira/browse/FINERACT-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1740. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to core module > --- > > Key: FINERACT-1740 > URL: https://issues.apache.org/jira/browse/FINERACT-1740 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in core module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- 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
]
Aleksandar Vidakovic updated FINERACT-1875:
---
Fix Version/s: 1.10.0
(was: 1.9.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.10.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
>
[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 ] Aleksandar Vidakovic updated FINERACT-1631: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.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] [Assigned] (FINERACT-1760) Manage external IDs
[
https://issues.apache.org/jira/browse/FINERACT-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic reassigned FINERACT-1760:
--
Assignee: Adam Saghy (was: Aleksandar Vidakovic)
> 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.9.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] [Resolved] (FINERACT-2001) Manage external IDs: Loan
[ https://issues.apache.org/jira/browse/FINERACT-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-2001. Resolution: Fixed > Manage external IDs: Loan > - > > Key: FINERACT-2001 > URL: https://issues.apache.org/jira/browse/FINERACT-2001 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Adam Saghy >Priority: Major > Fix For: 1.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-2002) Manage external IDs: Client
Aleksandar Vidakovic created FINERACT-2002: -- Summary: 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 Fix For: 1.10.0 -- 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
]
Aleksandar Vidakovic updated FINERACT-1760:
---
Fix Version/s: 1.10.0
(was: 1.9.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.10.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-1535) Migration from Mifos to Fineract
[ https://issues.apache.org/jira/browse/FINERACT-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1535: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.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-1549) Eclipse BIRT reporting module
[ https://issues.apache.org/jira/browse/FINERACT-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1549: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.0 > > -- 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 ] Aleksandar Vidakovic updated FINERACT-1142: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.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] [Created] (FINERACT-2001) Manage external IDs: Loan
Aleksandar Vidakovic created FINERACT-2001: -- Summary: Manage external IDs: Loan Key: FINERACT-2001 URL: https://issues.apache.org/jira/browse/FINERACT-2001 Project: Apache Fineract Issue Type: Sub-task Reporter: Aleksandar Vidakovic Assignee: Adam Saghy Fix For: 1.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=17779914#comment-17779914
]
Aleksandar Vidakovic commented on FINERACT-1245:
We should check if this is still an issue with version 7 of the generator tools.
> 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.10.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] [Resolved] (FINERACT-764) Run Integration Tests using Spring Boot IT support instead of on Tomcat started separately by gradle-tomcat-plugin
[
https://issues.apache.org/jira/browse/FINERACT-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic resolved FINERACT-764.
---
Resolution: Fixed
I think we can resolve this issue, because the current way the integration
tests are designed works. Using Testcontainers is a different topic (and has a
separate ticket FINERACT-1467).
> Run Integration Tests using Spring Boot IT support instead of on Tomcat
> started separately by gradle-tomcat-plugin
> --
>
> Key: FINERACT-764
> URL: https://issues.apache.org/jira/browse/FINERACT-764
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Michael Vorburger
>Assignee: Aleksandar Vidakovic
>Priority: Major
> Fix For: 1.9.0
>
>
> https://github.com/apache/fineract/pull/525 for FINERACT-700 struggles to get
> "./gradlew integrationTest" working under an up-to-date Gradle version, due
> to the gradle-tomcat-plugin failing to start Tomcat. The problem can also be
> seen (on that PR, as it stands right now) via {{./gradlew tomcatrunwar}}.
> https://github.com/bmuschko/gradle-tomcat-plugin mentions that its author "I
> don't have much time to contribute anymore. In practice this means far less
> activity, responsiveness on issues and new releases from my end."
> What we IMHO really should do instead is to ditch our use of
> gradle-tomcat-plugin and just use Spring Boot's very nice built-in support
> for Integration Test, see here:
> *
> https://docs.spring.io/spring-boot/docs/2.1.5.RELEASE/reference/htmlsingle/#boot-features-testing-spring-applications
> * https://www.baeldung.com/spring-boot-testing (see 7. Integration Testing
> with @SpringBootTest)
> * https://reflectoring.io/spring-boot-test/
> I wouldn't have time for this, but perhaps someone would like to pick this up?
--
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 ] Aleksandar Vidakovic updated FINERACT-1249: --- Summary: Re-introduce type safety in JAX-RS resource classes (was: Swagger YAML is invalid) > 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.9.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-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 ] Aleksandar Vidakovic updated FINERACT-1249: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.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-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
]
Aleksandar Vidakovic updated FINERACT-1245:
---
Fix Version/s: 1.10.0
(was: 1.9.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.10.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] [Commented] (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:comment-tabpanel=17779918#comment-17779918 ] Aleksandar Vidakovic commented on FINERACT-1249: Renamed the ticket to better reflect what we need to do. Fixing the current open api descript (aka swagger yaml file) is an ongoing manual effort anyway. > 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.10.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] [Resolved] (FINERACT-1482) Docker Hub Build broke with switch from Dockerfile to JIB
[ https://issues.apache.org/jira/browse/FINERACT-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1482. Resolution: Fixed I think this is resolved. We (James and myself) have also talked to the infrastructure team about this and they added our (Github) accounts with relevant privileges. > Docker Hub Build broke with switch from Dockerfile to JIB > - > > Key: FINERACT-1482 > URL: https://issues.apache.org/jira/browse/FINERACT-1482 > Project: Apache Fineract > Issue Type: Bug > Components: Build >Affects Versions: 1.6.0 >Reporter: Michael Vorburger >Assignee: Aleksandar Vidakovic >Priority: Blocker > Fix For: 1.9.0 > > > https://github.com/apache/fineract/commits/develop shows a lot of ugly red > crosses since recently. > I've had a look at why that is so, and one issue (together with another one > re. Sonar) is _ci/dockercloud-stage — Your image failed to build_. > I originally had set this up, see FINERACT-760 (and have access to the Docker > Hub Build Logs). > This is an impact of https://github.com/apache/fineract/pull/2009 for > FINERACT-1469, just like > https://github.com/vorburger/www.fineract.dev/issues/11. > I'm not going to be able to further look much into this myself, but perhaps > [~aleks] you would be interested in researching how this could be fixed? > If we cannot fix it (whether just time wise, or for some technical reasons), > then I would propose that we remove > https://hub.docker.com/repository/docker/apache/fineract/general. That may > warrant some discussion on the mailing list though - last time I looked at > the numbers (for ApacheCon) this container had HUGE (!) numbers of downloads. > A possible alternative could be to open up the container I'm anyway building > on https://www.fineract.dev and distribute that one instead? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (FINERACT-1989) Add Spring Modulith
[ https://issues.apache.org/jira/browse/FINERACT-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reopened FINERACT-1989: Needs still some polishing. > 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.9.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-1989) Add Spring Modulith
[ https://issues.apache.org/jira/browse/FINERACT-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1989: --- Fix Version/s: 1.10.0 (was: 1.9.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.10.0 > > > Automatic dependency diagram generation via Spring Modulith. Add module > documentation stubs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-2009) Upgrade latest framework libs
Aleksandar Vidakovic created FINERACT-2009: -- Summary: Upgrade latest framework libs Key: FINERACT-2009 URL: https://issues.apache.org/jira/browse/FINERACT-2009 Project: Apache Fineract Issue Type: Improvement Reporter: Aleksandar Vidakovic Assignee: Aleksandar Vidakovic Fix For: 1.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-2009) Upgrade latest framework libs
[ https://issues.apache.org/jira/browse/FINERACT-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-2009. Resolution: Fixed > Upgrade latest framework libs > - > > Key: FINERACT-2009 > URL: https://issues.apache.org/jira/browse/FINERACT-2009 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > Fix For: 1.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1979) Better versioning plugin for Gradle builds
Aleksandar Vidakovic created FINERACT-1979: -- Summary: Better versioning plugin for Gradle builds Key: FINERACT-1979 URL: https://issues.apache.org/jira/browse/FINERACT-1979 Project: Apache Fineract Issue Type: Improvement Reporter: Aleksandar Vidakovic Fix For: 1.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1979) Better versioning plugin for Gradle builds
[ https://issues.apache.org/jira/browse/FINERACT-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1979: -- Assignee: Aleksandar Vidakovic > Better versioning plugin for Gradle builds > -- > > Key: FINERACT-1979 > URL: https://issues.apache.org/jira/browse/FINERACT-1979 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > Fix For: 1.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1989) Add Spring Modulith
Aleksandar Vidakovic created FINERACT-1989: -- Summary: 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 Fix For: 1.9.0 Support developers to build well-structured components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1986) Modular Security Architecture: Phase 3
Aleksandar Vidakovic created FINERACT-1986: -- Summary: 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 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] [Created] (FINERACT-1984) Modular Security Architecture: Phase 1
Aleksandar Vidakovic created FINERACT-1984:
--
Summary: 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
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] [Created] (FINERACT-1985) Modular Security Architecture: Phase 2
Aleksandar Vidakovic created FINERACT-1985: -- Summary: Modular Security Architecture: Phase 2 Key: FINERACT-1985 URL: https://issues.apache.org/jira/browse/FINERACT-1985 Project: Apache Fineract Issue Type: Sub-task Reporter: Aleksandar Vidakovic Add dynamic OAuth client configuration (per tenant) for (any) OAuth compliant external ID server; use Keycloak as a default for tests (probably also recommended for production) etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1985) Modular Security Architecture: Phase 2
[ https://issues.apache.org/jira/browse/FINERACT-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1985: -- Assignee: Aleksandar Vidakovic > Modular Security Architecture: Phase 2 > -- > > Key: FINERACT-1985 > URL: https://issues.apache.org/jira/browse/FINERACT-1985 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.9.0, 1.10.0 > > > Add dynamic OAuth client configuration (per tenant) for (any) OAuth compliant > external ID server; use Keycloak as a default for tests (probably also > recommended for production) etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1985) Modular Security Architecture: Phase 2
[ https://issues.apache.org/jira/browse/FINERACT-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1985: --- Fix Version/s: (was: 1.9.0) > Modular Security Architecture: Phase 2 > -- > > Key: FINERACT-1985 > URL: https://issues.apache.org/jira/browse/FINERACT-1985 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.10.0 > > > Add dynamic OAuth client configuration (per tenant) for (any) OAuth compliant > external ID server; use Keycloak as a default for tests (probably also > recommended for production) etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1984) Modular Security Architecture: Phase 1
[
https://issues.apache.org/jira/browse/FINERACT-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic reassigned FINERACT-1984:
--
Assignee: Aleksandar Vidakovic
> 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
>
> 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] [Created] (FINERACT-1988) Modular Security Architecture: Phase 5
Aleksandar Vidakovic created FINERACT-1988: -- Summary: 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 Fix For: 1.10.0 Add Open Policy Agent based authorization module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1987) Modular Security Architecture: Phase 4
Aleksandar Vidakovic created FINERACT-1987: -- Summary: Modular Security Architecture: Phase 4 Key: FINERACT-1987 URL: https://issues.apache.org/jira/browse/FINERACT-1987 Project: Apache Fineract Issue Type: Sub-task Reporter: Aleksandar Vidakovic Add another authorization configuration based on OAuth and make the DB based "legacy" authorization module (phase 3) the default for releases (keeping 100% backwards compatibility); add documentation for OAuth based authorization and recommend for production systems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1987) Modular Security Architecture: Phase 4
[ https://issues.apache.org/jira/browse/FINERACT-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1987: -- Assignee: Aleksandar Vidakovic > Modular Security Architecture: Phase 4 > -- > > Key: FINERACT-1987 > URL: https://issues.apache.org/jira/browse/FINERACT-1987 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > > Add another authorization configuration based on OAuth and make the DB based > "legacy" authorization module (phase 3) the default for releases (keeping > 100% backwards compatibility); add documentation for OAuth based > authorization and recommend for production systems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1985) Modular Security Architecture: Phase 2
[ https://issues.apache.org/jira/browse/FINERACT-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1985: --- Fix Version/s: 1.9.0 1.10.0 > Modular Security Architecture: Phase 2 > -- > > Key: FINERACT-1985 > URL: https://issues.apache.org/jira/browse/FINERACT-1985 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Priority: Major > Fix For: 1.9.0, 1.10.0 > > > Add dynamic OAuth client configuration (per tenant) for (any) OAuth compliant > external ID server; use Keycloak as a default for tests (probably also > recommended for production) etc. -- 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 ] Aleksandar Vidakovic updated FINERACT-1986: --- Fix Version/s: 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 >Priority: Major > Fix For: 1.10.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-1984) Modular Security Architecture: Phase 1
[
https://issues.apache.org/jira/browse/FINERACT-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1984:
---
Fix Version/s: 1.9.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.9.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] [Assigned] (FINERACT-1986) Modular Security Architecture: Phase 3
[ https://issues.apache.org/jira/browse/FINERACT-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1986: -- Assignee: Aleksandar Vidakovic > 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.10.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-1987) Modular Security Architecture: Phase 4
[ https://issues.apache.org/jira/browse/FINERACT-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1987: --- Fix Version/s: 1.10.0 > Modular Security Architecture: Phase 4 > -- > > Key: FINERACT-1987 > URL: https://issues.apache.org/jira/browse/FINERACT-1987 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.10.0 > > > Add another authorization configuration based on OAuth and make the DB based > "legacy" authorization module (phase 3) the default for releases (keeping > 100% backwards compatibility); add documentation for OAuth based > authorization and recommend for production systems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1979) Better versioning plugin for Gradle builds
[ https://issues.apache.org/jira/browse/FINERACT-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1979. Resolution: Fixed > Better versioning plugin for Gradle builds > -- > > Key: FINERACT-1979 > URL: https://issues.apache.org/jira/browse/FINERACT-1979 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > Fix For: 1.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1484) Micrometer Monitoring Metrics with built-in Cloud Provider Out-Of-The-Box Support
[
https://issues.apache.org/jira/browse/FINERACT-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic reassigned FINERACT-1484:
--
Assignee: Aleksandar Vidakovic (was: Michael Vorburger)
> Micrometer Monitoring Metrics with built-in Cloud Provider Out-Of-The-Box
> Support
> -
>
> Key: FINERACT-1484
> URL: https://issues.apache.org/jira/browse/FINERACT-1484
> Project: Apache Fineract
> Issue Type: New Feature
>Reporter: Michael Vorburger
>Assignee: Aleksandar Vidakovic
>Priority: Major
> Fix For: 1.9.0
>
>
> See e.g. https://micrometer.io for what this issue is all about.
> The goal is just to get
> "[standard|https://docs.spring.io/spring-boot/docs/current/reference/html/actuator.html#actuator.metrics.supported];
> out-of-the-box metrics support [working seamlessly and automagically on
> Cloud Providers such as
> GCP|https://cloud.spring.io/spring-cloud-gcp/reference/html/#stackdriver-monitoring]
> (e.g. for https://www.fineract.dev), but not [Custom
> Metrics|http://example.com] - yet, although others could build those on top
> of this initial feature, later.
> Perhaps it could be neat if {{/actuator/metrics}} allow easily "seeing" those
> with a development Spring Profile locally for testing and a YouTube ;-) demo?
> In production, e.g. on https://demo.fineract.dev/fineract-provider/actuator/,
> this should NEVER be enable however, of course.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FINERACT-1999) Publish snapshot versions without signing
Aleksandar Vidakovic created FINERACT-1999:
--
Summary: Publish snapshot versions without signing
Key: FINERACT-1999
URL: https://issues.apache.org/jira/browse/FINERACT-1999
Project: Apache Fineract
Issue Type: Improvement
Reporter: Aleksandar Vidakovic
Assignee: Aleksandar Vidakovic
Fix For: 1.9.0
if (!project.hasProperty('unofficialPublish')) \{
apply plugin: 'signing'
}
if (!project.hasProperty('unofficialPublish')) \{
signing {
sign publishing.publications.mavenJava
}
}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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 ] Aleksandar Vidakovic updated FINERACT-1575: --- Fix Version/s: 1.7.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.7.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.7#820007)
[jira] [Assigned] (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 ] Aleksandar Vidakovic reassigned FINERACT-1575: -- Assignee: Aleksandar Vidakovic (was: Victor Romero) > 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: Aleksandar Vidakovic >Priority: Major > Fix For: 1.7.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.7#820007)
[jira] [Assigned] (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 ] Aleksandar Vidakovic reassigned FINERACT-1575: -- Assignee: Victor Romero (was: Aleksandar Vidakovic) > 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.7.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.7#820007)
[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 ] Aleksandar Vidakovic updated FINERACT-1577: --- Fix Version/s: 1.7.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.7.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1590) Release Apache Fineract 1.7.0
[ https://issues.apache.org/jira/browse/FINERACT-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1590: --- Description: Umbrella issue for tracking all activity for this Fineract release 1.7.0 > Release Apache Fineract 1.7.0 > - > > Key: FINERACT-1590 > URL: https://issues.apache.org/jira/browse/FINERACT-1590 > Project: Apache Fineract > Issue Type: Task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.7.0 > > > Umbrella issue for tracking all activity for this Fineract release 1.7.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1590) Release Apache Fineract 1.7.0
[ https://issues.apache.org/jira/browse/FINERACT-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1590: --- Fix Version/s: (was: 1.7.0) > Release Apache Fineract 1.7.0 > - > > Key: FINERACT-1590 > URL: https://issues.apache.org/jira/browse/FINERACT-1590 > Project: Apache Fineract > Issue Type: Task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > > Umbrella issue for tracking all activity for this Fineract release 1.7.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (FINERACT-1576) GCP Cloud SQL Support
[ https://issues.apache.org/jira/browse/FINERACT-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1576: -- Assignee: Victor Romero (was: Aleksandar Vidakovic) > GCP Cloud SQL Support > - > > Key: FINERACT-1576 > URL: https://issues.apache.org/jira/browse/FINERACT-1576 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Fix For: 1.7.0 > > > GCP Cloud SQL Support has advantage for using a fully managed SQL > environment, Cloud SQL on GCP supports MySQL & Postgresql -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (FINERACT-1576) GCP Cloud SQL Support
[ https://issues.apache.org/jira/browse/FINERACT-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1576: -- Assignee: Aleksandar Vidakovic (was: Victor Romero) > GCP Cloud SQL Support > - > > Key: FINERACT-1576 > URL: https://issues.apache.org/jira/browse/FINERACT-1576 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Victor Romero >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.7.0 > > > GCP Cloud SQL Support has advantage for using a fully managed SQL > environment, Cloud SQL on GCP supports MySQL & Postgresql -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1576) GCP Cloud SQL Support
[ https://issues.apache.org/jira/browse/FINERACT-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1576: --- Fix Version/s: 1.7.0 > GCP Cloud SQL Support > - > > Key: FINERACT-1576 > URL: https://issues.apache.org/jira/browse/FINERACT-1576 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Fix For: 1.7.0 > > > GCP Cloud SQL Support has advantage for using a fully managed SQL > environment, Cloud SQL on GCP supports MySQL & Postgresql -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (FINERACT-1590) Release Apache Fineract 1.7.0
Aleksandar Vidakovic created FINERACT-1590: -- Summary: Release Apache Fineract 1.7.0 Key: FINERACT-1590 URL: https://issues.apache.org/jira/browse/FINERACT-1590 Project: Apache Fineract Issue Type: Task Reporter: Aleksandar Vidakovic Assignee: Aleksandar Vidakovic Fix For: 1.7.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (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 ] Aleksandar Vidakovic reassigned FINERACT-1577: -- Assignee: Victor Romero (was: Aleksandar Vidakovic) > 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.7.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (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 ] Aleksandar Vidakovic reassigned FINERACT-1577: -- Assignee: Aleksandar Vidakovic (was: Victor Romero) > 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: Aleksandar Vidakovic >Priority: Major > Fix For: 1.7.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (FINERACT-1593) Unable to Create New Client
[ https://issues.apache.org/jira/browse/FINERACT-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1593: -- Assignee: Arnold Galovics > Unable to Create New Client > > > Key: FINERACT-1593 > URL: https://issues.apache.org/jira/browse/FINERACT-1593 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.6.1, 1.7.0 > Environment: Ubuntu 20.04 LTS , Fineract Latest Development Branch , > Tomcat 9.0.60 >Reporter: Rajarshi Singha >Assignee: Arnold Galovics >Priority: Critical > Fix For: 1.7.0 > > Attachments: Catalina error log.txt, error log console.txt > > > Unable to create client in Fineract Development Branch after ElicpseLink > Upgrade, > its throwing error 500 . > added catalina.out log , console error log -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1593) Unable to Create New Client
[ https://issues.apache.org/jira/browse/FINERACT-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1593: --- Fix Version/s: 1.7.0 > Unable to Create New Client > > > Key: FINERACT-1593 > URL: https://issues.apache.org/jira/browse/FINERACT-1593 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.6.1, 1.7.0 > Environment: Ubuntu 20.04 LTS , Fineract Latest Development Branch , > Tomcat 9.0.60 >Reporter: Rajarshi Singha >Priority: Critical > Fix For: 1.7.0 > > Attachments: Catalina error log.txt, error log console.txt > > > Unable to create client in Fineract Development Branch after ElicpseLink > Upgrade, > its throwing error 500 . > added catalina.out log , console error log -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1497) Unable to generate Swagger API on Windows
[
https://issues.apache.org/jira/browse/FINERACT-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1497:
---
Fix Version/s: 1.6.0
(was: 1.7.0)
> Unable to generate Swagger API on Windows
> -
>
> Key: FINERACT-1497
> URL: https://issues.apache.org/jira/browse/FINERACT-1497
> Project: Apache Fineract
> Issue Type: Bug
> Environment: Windows 10
>Reporter: Arnold Galovics
>Assignee: Arnold Galovics
>Priority: Major
> Fix For: 1.6.0
>
>
> *Repro steps:*
> # Start your Windows machine
> # Check out the code to a local folder
> # Execute the following command
> {code:java}
> $ ./gradlew clean test{code}
> # Error happens that the swagger file could not be found
> *Proposed solution:*
> In fineract-client, instead of using the
> {code:java}
> inputSpec = "file://$swaggerFile" {code}
>
> format, use the following one (without _file://)_
> {code:java}
> inputSpec = "$swaggerFile" {code}
> *Error logs:*
>
> {code:java}
> $ ./gradlew clean test
> > Task :fineract-provider:compileJava
> Found no persistent property in
> "org.apache.fineract.infrastructure.dataqueries.domain.ReportParameter"> Task
> :fineract-client:buildJavaSdk
> Exception while reading:
> java.lang.RuntimeException: Could not find
> file://C:/Users//fineract/fineract-provider/build/generated/swagger-ui/fineract.yaml
> on the classpath
> at
> io.swagger.v3.parser.util.ClasspathHelper.loadFileFromClasspath(ClasspathHelper.java:31)
> at
> io.swagger.v3.parser.OpenAPIV3Parser.readWithInfo(OpenAPIV3Parser.java:150)
> at
> io.swagger.v3.parser.OpenAPIV3Parser.readLocation(OpenAPIV3Parser.java:59)
> at io.swagger.parser.OpenAPIParser.readLocation(OpenAPIParser.java:16)
> at
> org.openapitools.codegen.config.CodegenConfigurator.toContext(CodegenConfigurator.java:461)
> at
> org.openapitools.codegen.config.CodegenConfigurator.toClientOptInput(CodegenConfigurator.java:507)
> at
> org.openapitools.generator.gradle.plugin.tasks.GenerateTask.doWork(GenerateTask.kt:634)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
> at
> org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
> ...
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:61)
> at java.base/java.lang.Thread.run(Thread.java:833)
> failed to read resource listing
> java.lang.RuntimeException: Could not find
> file://C:/Users//fineract/fineract-provider/build/generated/swagger-ui/fineract.yaml
> on the classpath
> at
> io.swagger.parser.util.ClasspathHelper.loadFileFromClasspath(ClasspathHelper.java:31)
> at
> io.swagger.parser.SwaggerCompatConverter.readResourceListing(SwaggerCompatConverter.java:207)
> at
> io.swagger.parser.SwaggerCompatConverter.read(SwaggerCompatConverter.java:123)
> at
> io.swagger.parser.SwaggerCompatConverter.readWithInfo(SwaggerCompatConverter.java:94)
> at io.swagger.parser.SwaggerParser.readWithInfo(SwaggerParser.java:42)
> at
> io.swagger.v3.parser.converter.SwaggerConverter.readLocation(SwaggerConverter.java:89)
> at io.swagger.parser.OpenAPIParser.readLocation(OpenAPIParser.java:16)
> at
> org.openapitools.codegen.config.CodegenConfigurator.toContext(CodegenConfigurator.java:461)
> at
> org.openapitools.codegen.config.CodegenConfigurator.toClientOptInput(CodegenConfigurator.java:507)
> at
> org.openapitools.generator.gradle.plugin.tasks.GenerateTask.doWork(GenerateTask.kt:634)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
> at
>
[jira] [Commented] (FINERACT-1592) Hikari Pool connection timed out. Tomcat crushes users cannot log in after
[ https://issues.apache.org/jira/browse/FINERACT-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17526944#comment-17526944 ] Aleksandar Vidakovic commented on FINERACT-1592: I've added FINERACT-1593 as a blocker to the upcoming release 1.7.0. We need to fix this. The rest of the conversation I've read as "Hikari misconfiguration". If there's an issue though then please correct me; or even better: create a Jira ticket with "fixVersions" 1.7 and mark it as blocker. Can we make sure that we speak about the same issue here though? This seems to be a EclipseLink related problem... so when I read "version 1.6" then something is wrong... 1.6 is still running on OpenJPA... I know that people like to use the current develop branch as an equivalent to the latest release (1.6 in this case)... this doesn't fly here, because of the substantial changes... just FYI > Hikari Pool connection timed out. Tomcat crushes users cannot log in after > -- > > Key: FINERACT-1592 > URL: https://issues.apache.org/jira/browse/FINERACT-1592 > Project: Apache Fineract > Issue Type: Bug > Components: Performance, Reports >Affects Versions: 1.6.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-04-22-11-25-32-303.png > > > !image-2022-04-22-11-25-32-303.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-984) Postgres support
[ https://issues.apache.org/jira/browse/FINERACT-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-984: -- Fix Version/s: 1.7.0 > Postgres support > > > Key: FINERACT-984 > URL: https://issues.apache.org/jira/browse/FINERACT-984 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Michael Vorburger >Assignee: Arnold Galovics >Priority: Major > Fix For: 1.7.0 > > > [~ptuomola] in FINERACT-982 brought up if Fineract (non-CN) has looked at > Postgres support? > I'm not sure what the effort is, but someone motivated sure could try it out. > The Postgres JDBC driver is BSD licenses, which is fine for the ASF. > Personally I'd probably suggest "instead" not "in addition" to MySQL - but > that requires a data migration tool. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (FINERACT-984) Postgres support
[ https://issues.apache.org/jira/browse/FINERACT-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-984. --- Resolution: Fixed > Postgres support > > > Key: FINERACT-984 > URL: https://issues.apache.org/jira/browse/FINERACT-984 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Michael Vorburger >Assignee: Arnold Galovics >Priority: Major > Fix For: 1.7.0 > > > [~ptuomola] in FINERACT-982 brought up if Fineract (non-CN) has looked at > Postgres support? > I'm not sure what the effort is, but someone motivated sure could try it out. > The Postgres JDBC driver is BSD licenses, which is fine for the ASF. > Personally I'd probably suggest "instead" not "in addition" to MySQL - but > that requires a data migration tool. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1593) Unable to Create New Client
[ https://issues.apache.org/jira/browse/FINERACT-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1593: --- Priority: Blocker (was: Critical) > Unable to Create New Client > > > Key: FINERACT-1593 > URL: https://issues.apache.org/jira/browse/FINERACT-1593 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.6.1, 1.7.0 > Environment: Ubuntu 20.04 LTS , Fineract Latest Development Branch , > Tomcat 9.0.60 >Reporter: Rajarshi Singha >Assignee: Arnold Galovics >Priority: Blocker > Fix For: 1.7.0 > > Attachments: Catalina error log.txt, error log console.txt > > > Unable to create client in Fineract Development Branch after ElicpseLink > Upgrade, > its throwing error 500 . > added catalina.out log , console error log -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1499) Exception while Startup : Driver org.mariadb.jdbc.Driver claims to not accept jdbcUrl, 'jdbc:mariadb://localhost:3306/fineract_tenants'
[ https://issues.apache.org/jira/browse/FINERACT-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1499: --- Fix Version/s: 1.6.0 > Exception while Startup : Driver org.mariadb.jdbc.Driver claims to not accept > jdbcUrl, 'jdbc:mariadb://localhost:3306/fineract_tenants' > --- > > Key: FINERACT-1499 > URL: https://issues.apache.org/jira/browse/FINERACT-1499 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.6.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Major > Fix For: 1.6.0 > > > > While starting fineract with Maria DB, Fineract is not able to connect to DB. > This happened while running > ./gradlew clean bootRun > on local dev environment with Ubuntu 20.4. > the following exception is thrown > > org.springframework.beans.BeanInstantiationException: Failed to instantiate > [javax.sql.DataSource]: Factory method 'hikariTenantDataSource' threw > exception; nested exception is java.lang.RuntimeException: Driver > org.mariadb.jdbc.Driver claims to not accept jdbcUrl, > 'jdbc:mariadb://localhost:3306/fineract_tenants' > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:653) > ... 137 common frames omitted > Caused by: java.lang.RuntimeException: Driver org.mariadb.jdbc.Driver claims > to not accept jdbcUrl, 'jdbc:mariadb://localhost:3306/fineract_tenants' > at > com.zaxxer.hikari.util.DriverDataSource.(DriverDataSource.java:110) > at > com.zaxxer.hikari.pool.PoolBase.initializeDataSource(PoolBase.java:331) > at com.zaxxer.hikari.pool.PoolBase.(PoolBase.java:114) > at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:108) > at com.zaxxer.hikari.HikariDataSource.(HikariDataSource.java:81) > at > org.apache.fineract.infrastructure.core.config.HikariCpConfig.hikariTenantDataSource(HikariCpConfig.java:45) > at > org.apache.fineract.infrastructure.core.config.HikariCpConfig$$EnhancerBySpringCGLIB$$f2ef3540.CGLIB$hikariTenantDataSource$1() > at > org.apache.fineract.infrastructure.core.config.HikariCpConfig$$EnhancerBySpringCGLIB$$f2ef3540$$FastClassBySpringCGLIB$$8fc6d73d.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331) > at > org.apache.fineract.infrastructure.core.config.HikariCpConfig$$EnhancerBySpringCGLIB$$f2ef3540.hikariTenantDataSource() > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:568) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154) > ... 138 common frames omitted -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1498) Liquibase support
[ https://issues.apache.org/jira/browse/FINERACT-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1498: --- Fix Version/s: 1.7.0 > Liquibase support > - > > Key: FINERACT-1498 > URL: https://issues.apache.org/jira/browse/FINERACT-1498 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Arnold Galovics >Assignee: Arnold Galovics >Priority: Major > Fix For: 1.7.0 > > > Switch to Liquibase schema migration instead of Flyway in order to be > database-independent for schema migrations. > > This is especially needed for bringing in PostgreSQL support on top of the > current MySQL support. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1502) To support Webhooks with all paths instead of only absolute path
[
https://issues.apache.org/jira/browse/FINERACT-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1502:
---
Fix Version/s: 1.7.0
> To support Webhooks with all paths instead of only absolute path
>
>
> Key: FINERACT-1502
> URL: https://issues.apache.org/jira/browse/FINERACT-1502
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Sandeep
>Assignee: Sandeep
>Priority: Major
> Fix For: 1.7.0
>
> Attachments: WebhookAPICallUpdatesURL.png
>
>
> Current Implementation supports Webhook URL with absolute path like
> [https://www.hostname.com|https://www.hostname.com/] but it does not support
> urls like [https://www.hostname.com/v1/api/webhook/] or
> [https://www.hostname.com/webhook/]
> *Currently Webhook URLs working* : Only AbsoluteUrls as baseURL
> ([http://www.hostname.com/])
> *URLs Not working* : Relative Paths in baseURL like
> [http://www.hostname.com/v1/api/webhook]
> *Root Cause :* This problem is happening due to retrofit2 library as it
> removes relative path from baseURL due to "/" present in request like
> Get("/") , POST("/") etc. So it updates
> [http://www.hostname.com/v1/api/webhook] to [http://www.hostname.com/] while
> making API call and hence we get 404 error.
> Please refer attached screenshots for same where i printed baseURL in logs,
> So baseURL was updated during api call and hence it is resulting in 404 error
> *Resolution* :
> So in order to support absolute url as well as all other relative URL Paths,
> I updated Webhook Service Code and replaced GET("/") by GET(".") So that
> retrofit2 library does not remove anything from baseURL. I tested code and it
> is working fine with both kind of URLs.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (FINERACT-1495) Savings Interest posting Performance improvement
[ https://issues.apache.org/jira/browse/FINERACT-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1495: --- Fix Version/s: 1.6.0 (was: 1.8.0) > Savings Interest posting Performance improvement > > > Key: FINERACT-1495 > URL: https://issues.apache.org/jira/browse/FINERACT-1495 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.6.0 > > > improve savings interest posting job performance -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (FINERACT-1495) Savings Interest posting Performance improvement
[ https://issues.apache.org/jira/browse/FINERACT-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1495. Resolution: Fixed > Savings Interest posting Performance improvement > > > Key: FINERACT-1495 > URL: https://issues.apache.org/jira/browse/FINERACT-1495 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.6.0 > > > improve savings interest posting job performance -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINERACT-1496) Improve performance for loading a Loan
[ https://issues.apache.org/jira/browse/FINERACT-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1496: --- Fix Version/s: 1.6.0 (was: 1.7.0) > Improve performance for loading a Loan > -- > > Key: FINERACT-1496 > URL: https://issues.apache.org/jira/browse/FINERACT-1496 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Arnold Galovics >Assignee: Arnold Galovics >Priority: Major > Fix For: 1.6.0 > > > With the current implementation and the configured JPA associations, when > loading a single Loan entity from the database through JPA, it'll eagerly > fetch all the related LoanCollateralManagement entities. > Generally speaking we should aim to avoid EAGER loading to prevent > performance bottlenecks to form and we should only use it in places where > it's really justified. > > Unfortunately by marking this Loan -> LoanCollateralManagement relationship > eagerly fetched it starts kind of a chain reaction of loading a lot more data > than needed. > The whole relationship chain looks the following: > Loan -> LoanCollateralManagement -> ClientCollateralManagement -> > CollateralManagementDomain -> ApplicationCurrency > That's a huge slice of data. > > The idea of this ticket is to adjust this behavior and switch the Loan -> > LoanCollateralManagement relationship to be a LAZY relationship so different > use cases have the chance to fetch only the data they'll need. > This will definitely speed up the Loan related operations. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (FINERACT-1592) Hikari Pool connection timed out. Tomcat crushes users cannot log in after
[ https://issues.apache.org/jira/browse/FINERACT-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527150#comment-17527150 ] Aleksandar Vidakovic commented on FINERACT-1592: [~erprince] could you provide values before and after you made the change. Or even better: could you create a pull request referencing this issue so that we can properly review? It's harder to follow the conversation here without code and actual values. Thanks. > Hikari Pool connection timed out. Tomcat crushes users cannot log in after > -- > > Key: FINERACT-1592 > URL: https://issues.apache.org/jira/browse/FINERACT-1592 > Project: Apache Fineract > Issue Type: Bug > Components: Performance, Reports >Affects Versions: 1.6.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-04-22-11-25-32-303.png > > > !image-2022-04-22-11-25-32-303.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (FINERACT-1592) Hikari Pool connection timed out. Tomcat crushes users cannot log in after
[ https://issues.apache.org/jira/browse/FINERACT-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527150#comment-17527150 ] Aleksandar Vidakovic edited comment on FINERACT-1592 at 4/24/22 11:54 AM: -- [~erprince] could you provide values before and after you made the change. Or even better: could you create a pull request referencing this issue so that we can properly review? It's harder to follow the conversation here without code and actual values. Thanks. Having said that: I am a bit surprised that there is a problem in the Hikari configuration. The values are exactly the same as the ones we had previously, just not hard-coded. If we have a problem now with these values and then we should have had an issue in previous releases too. But let's have a look at a pull request and then we can see more. was (Author: aleks): [~erprince] could you provide values before and after you made the change. Or even better: could you create a pull request referencing this issue so that we can properly review? It's harder to follow the conversation here without code and actual values. Thanks. > Hikari Pool connection timed out. Tomcat crushes users cannot log in after > -- > > Key: FINERACT-1592 > URL: https://issues.apache.org/jira/browse/FINERACT-1592 > Project: Apache Fineract > Issue Type: Bug > Components: Performance, Reports >Affects Versions: 1.6.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-04-22-11-25-32-303.png > > > !image-2022-04-22-11-25-32-303.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (FINERACT-1592) Hikari Pool connection timed out. Tomcat crushes users cannot log in after
[ https://issues.apache.org/jira/browse/FINERACT-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527195#comment-17527195 ] Aleksandar Vidakovic commented on FINERACT-1592: Appreciate it [~erprince] > Hikari Pool connection timed out. Tomcat crushes users cannot log in after > -- > > Key: FINERACT-1592 > URL: https://issues.apache.org/jira/browse/FINERACT-1592 > Project: Apache Fineract > Issue Type: Bug > Components: Performance, Reports >Affects Versions: 1.6.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-04-22-11-25-32-303.png > > > !image-2022-04-22-11-25-32-303.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (FINERACT-1592) Hikari Pool connection timed out. Tomcat crushes users cannot log in after
[ https://issues.apache.org/jira/browse/FINERACT-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527252#comment-17527252 ] Aleksandar Vidakovic commented on FINERACT-1592: Alright, thanks for the feedback [~erprince] . The value though seems a bit arbitrary... could it be that it's only a problem in your specific situation? Maybe the database is running on a slower machine... maybe it's a shared database... maybe there's a bigger latency between the Fineract node and the database... or maybe you just have an exceptionally high amount of users? How can we be sure that 4 and not 6 is the value? What I want to say is that I'm always a bit suspicious when increasing timeouts solves something... well, let me be more precise: the 2 are just a value that should work for a demo system with Docker Compose and I'm pretty sure it does that (again, those values are exactly the same that we had previously hard-coded in the Hikari setup. The only difference now is that you have a choice of changing those values without changing sources. So, what I think the situation here is: that you adjusted that value for your specific setup (good, that's what we have those variables now for)... but this doesn't make the default value a "bug". It would be different if you said that the situation with the starving transactions is happening on your local machine, Fineract started with Docker Compose and you use the community app (alone as a single user)... that would be something to worry about. Having said all that: if you could give a little bit more context (is this happening in a production system? behind a proxy? load balancer? how many users?) then we could add this information to the documentation... this would be great and valuable information for other's to be able to adjust those values for their setups. Information like this would be great for the documentation. > Hikari Pool connection timed out. Tomcat crushes users cannot log in after > -- > > Key: FINERACT-1592 > URL: https://issues.apache.org/jira/browse/FINERACT-1592 > Project: Apache Fineract > Issue Type: Bug > Components: Performance, Reports >Affects Versions: 1.6.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-04-22-11-25-32-303.png > > > !image-2022-04-22-11-25-32-303.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (FINERACT-1592) Hikari Pool connection timed out. Tomcat crushes users cannot log in after
[ https://issues.apache.org/jira/browse/FINERACT-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527255#comment-17527255 ] Aleksandar Vidakovic commented on FINERACT-1592: Excellent... so the context so far is: * production environment * Pentaho included * running reports FYI: I am currently working on improving the documentation... and one of the (many) things we should add is recommendations for production use. And this here is clearly a candidate topic for that chapter. So, if everybody agrees here I'd change this Jira ticket from a bug to a task and change to title to something like "Add chapter for running in production to documentation" (I'm not the best with titles) or close this ticket here with "WONTFIX". My vote would be on the documentation, then we don't lose all this valuable information and others can profit of your discoveries. Please let me know what you want to do. > Hikari Pool connection timed out. Tomcat crushes users cannot log in after > -- > > Key: FINERACT-1592 > URL: https://issues.apache.org/jira/browse/FINERACT-1592 > Project: Apache Fineract > Issue Type: Bug > Components: Performance, Reports >Affects Versions: 1.6.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-04-22-11-25-32-303.png > > > !image-2022-04-22-11-25-32-303.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
