[jira] [Commented] (FINERACT-1261) support for external Oauth provider
[ https://issues.apache.org/jira/browse/FINERACT-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378395#comment-17378395 ] Aleksandar Vidakovic commented on FINERACT-1261: Intending to add support for Auth0 and Keykloak. FYI. > support for external Oauth provider > > > Key: FINERACT-1261 > URL: https://issues.apache.org/jira/browse/FINERACT-1261 > Project: Apache Fineract > Issue Type: Improvement > Components: Security >Affects Versions: 1.4.0 >Reporter: Vincent FUCHS >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.6.0 > > > Hi, > > I was looking at the couple of tickets open around OAuth2 support, mostly > https://issues.apache.org/jira/browse/FINERACT-1142 (and its related issues) > and https://issues.apache.org/jira/browse/FINERACT-1012 , and from what I > understand, we currently have no way to configure an external OAuth provider. > Is that correct ? > > A typical Oauth flow is to authenticate against a standard provider, using > the provider login page and get an OAuth token and be redirected, then use > that token in all the requests. The security layer then checks the token > validity for all incoming requests. > > Spring has fairly standard support for this : > [https://spring.io/guides/tutorials/spring-boot-oauth2/] > > Is it something that works but is not documented ? or is it sure that it > doesn't currently work ? > (I would assume that once https://issues.apache.org/jira/browse/FINERACT-1012 > is completed, it will just be a matter of providing the right Spring > properties values) > > Thanks > > -- > Vincent > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1261) support for external Oauth provider
[ https://issues.apache.org/jira/browse/FINERACT-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1261: --- Fix Version/s: 1.6.0 > support for external Oauth provider > > > Key: FINERACT-1261 > URL: https://issues.apache.org/jira/browse/FINERACT-1261 > Project: Apache Fineract > Issue Type: Improvement > Components: Security >Affects Versions: 1.4.0 >Reporter: Vincent FUCHS >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.6.0 > > > Hi, > > I was looking at the couple of tickets open around OAuth2 support, mostly > https://issues.apache.org/jira/browse/FINERACT-1142 (and its related issues) > and https://issues.apache.org/jira/browse/FINERACT-1012 , and from what I > understand, we currently have no way to configure an external OAuth provider. > Is that correct ? > > A typical Oauth flow is to authenticate against a standard provider, using > the provider login page and get an OAuth token and be redirected, then use > that token in all the requests. The security layer then checks the token > validity for all incoming requests. > > Spring has fairly standard support for this : > [https://spring.io/guides/tutorials/spring-boot-oauth2/] > > Is it something that works but is not documented ? or is it sure that it > doesn't currently work ? > (I would assume that once https://issues.apache.org/jira/browse/FINERACT-1012 > is completed, it will just be a matter of providing the right Spring > properties values) > > Thanks > > -- > Vincent > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1261) support for external Oauth provider
[ https://issues.apache.org/jira/browse/FINERACT-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1261: -- Assignee: Aleksandar Vidakovic > support for external Oauth provider > > > Key: FINERACT-1261 > URL: https://issues.apache.org/jira/browse/FINERACT-1261 > Project: Apache Fineract > Issue Type: Improvement > Components: Security >Affects Versions: 1.4.0 >Reporter: Vincent FUCHS >Assignee: Aleksandar Vidakovic >Priority: Major > > Hi, > > I was looking at the couple of tickets open around OAuth2 support, mostly > https://issues.apache.org/jira/browse/FINERACT-1142 (and its related issues) > and https://issues.apache.org/jira/browse/FINERACT-1012 , and from what I > understand, we currently have no way to configure an external OAuth provider. > Is that correct ? > > A typical Oauth flow is to authenticate against a standard provider, using > the provider login page and get an OAuth token and be redirected, then use > that token in all the requests. The security layer then checks the token > validity for all incoming requests. > > Spring has fairly standard support for this : > [https://spring.io/guides/tutorials/spring-boot-oauth2/] > > Is it something that works but is not documented ? or is it sure that it > doesn't currently work ? > (I would assume that once https://issues.apache.org/jira/browse/FINERACT-1012 > is completed, it will just be a matter of providing the right Spring > properties values) > > Thanks > > -- > Vincent > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-330) Import rule based in the API.
[ https://issues.apache.org/jira/browse/FINCN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-330: - Assignee: Yemdjih Kaze Nasser > Import rule based in the API. > - > > Key: FINCN-330 > URL: https://issues.apache.org/jira/browse/FINCN-330 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Import and implement and test rule based scoring in the API module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-982) Completely ditch use of Drizzle JDBC Driver after all
[ https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-982: Assignee: (was: Yemdjih Kaze Nasser) > Completely ditch use of Drizzle JDBC Driver after all > - > > Key: FINERACT-982 > URL: https://issues.apache.org/jira/browse/FINERACT-982 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Priority: Blocker > Labels: scalability > Fix For: 1.6.0 > > > Fineract's use of the un-maintained Drizzle JDBC driver continues to cause > confusion and pains like FINERACT-980, and note e.g. the proposed removal of > the alternative MySQL JDBC driver in > [https://github.com/apache/fineract/pull/887.] > Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and > LEGAL-462. > LEGAL-462 has clarified that the Fineract ZIP distribution must include > Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and > currently (given the confusion in FINERACT-980 apparently do?!) use it for > tests. > What if to reduce variability we just removed that old Drizzle JDBC driver > after all? We could run our tests using (preferably) the very well maintained > MariaDB JDBC driver client (the actual DB server is a totally separate > discussion, see FINERACT-896). We would (have to) distribute the ZIP for > download without a JDBC driver, and just some documentation inviting users to > DL and add one. > But the exact situation about distributing in a Docker container image isn't > clear, to me... > FYI [~awasum], [~ptuomola], [~xurror] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1140) Adopt GenerationType.TABLE as ID generation strategy
[ https://issues.apache.org/jira/browse/FINERACT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-1140. --- Resolution: Won't Do > Adopt GenerationType.TABLE as ID generation strategy > > > Key: FINERACT-1140 > URL: https://issues.apache.org/jira/browse/FINERACT-1140 > Project: Apache Fineract > Issue Type: Test >Affects Versions: 1.5.0 >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Working with eclipselink, I noticed there were situations where when trying > to persist objects with sub entities, the IDs of the sub entities where not > generated fast enough making the ID column to always be set to null causing a > lot SQLIntegrityViolations. > As a solution of last resort I experimented with table generation strategy > which is able to set ID upon object creation instead of at persist time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1322) Add Support for a Bi Monthly Loan Product
[ https://issues.apache.org/jira/browse/FINERACT-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1322: - Assignee: (was: Yemdjih Kaze Nasser) > Add Support for a Bi Monthly Loan Product > - > > Key: FINERACT-1322 > URL: https://issues.apache.org/jira/browse/FINERACT-1322 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Reporter: Yemdjih Kaze Nasser >Priority: Major > Fix For: 1.6.0 > > > Add the ability to create a loan that is collected twice a month. Date > selection would be one of two options > Two dates selected for each month: default dates are already part of this > ensemble i.e 15th and 30th, 10th and 25th > These date combinations may change midway for e,g 10/25 may become 15/30, > Which means we can edit the loan product’ First and second date thus > affecting the schedule change from that day. -- This message was sent by Atlassian Jira (v8.3.4#803005)
