[
https://issues.apache.org/jira/browse/FINERACT-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136038#comment-18136038
]
Thevinu Jayasekara edited comment on FINERACT-2982 at 11/1/26, 9:15 AM:
------------------------------------------------------------------------
Hi all,
I'll take the client activation path that [~danhan] found while working on
[#6777|https://github.com/apache/fineract/pull/6777]. Activating a client with
a default savings product (activateClient → createActiveApplication) creates an
active savings account and posts the minimum opening balance, but client
activation doesn't check the user's office.
I'll raise it as a separate small PR so it doesn't add to #6798.
Current PRs for this ticket:
- Account activation (savings / FD / RD): #6777
- Remaining loan operations, share accounts, working capital loans: #6798
- Capitalized income: #6799
- Client activation: coming next
Thanks!
was (Author: JIRAUSER315052):
Hi all,
I'll take the client activation path that [~danhan] found while working on
#6777. Activating a client with a default savings product (activateClient →
createActiveApplication) creates an active savings account and posts the
minimum opening balance, but client activation doesn't check the user's office.
I'll raise it as a separate small PR so it doesn't add to #6798.
Current PRs for this ticket:
- Account activation (savings / FD / RD): #6777
- Remaining loan operations, share accounts, working capital loans: #6798
- Capitalized income: #6799
- Client activation: coming next
Thanks!
> Extend office-hierarchy access checks to remaining monetary operations
> ----------------------------------------------------------------------
>
> Key: FINERACT-2982
> URL: https://issues.apache.org/jira/browse/FINERACT-2982
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Thevinu Jayasekara
> Priority: Major
>
> FINERACT-2639 (PR [#6698|https://github.com/apache/fineract/pull/6698]) added
> office-hierarchy checks to loan, savings, account transfer, fixed/recurring
> deposit and collection sheet transactions. A user can only post them on
> accounts in their own office or a child office.
> The following operations can still create money-bearing transactions on
> accounts outside
> the user's office hierarchy:
> * Account activation that posts an initial deposit: savings, fixed deposit,
> recurring deposit
> (SavingsAccountWritePlatformServiceJpaRepositoryImpl.activate,
> DepositAccountWritePlatformServiceJpaRepositoryImpl.activateFDAccount /
> activateRDAccount)
> * Capitalized income (CapitalizedIncomeWritePlatformServiceImpl)
> * Buy-down fee (BuyDownFeeWritePlatformServiceImpl)
> * Re-age and re-amortize (LoanReAgingService, LoanReAmortizationService)
> * Interest pause (InterestPauseWritePlatformServiceImpl)
> * Contract termination (LoanContractTerminationServiceImpl)
> * Working-capital loans: repayment, charge-off and related write services in
> fineract-working-capital-loan
> * Share accounts (ShareAccountWritePlatformServiceJpaRepositoryImpl)
> Expected: these user-triggered operations use the same in-user-scope loaders
> as FINERACT-2639, so a user outside the account's office hierarchy gets a
> 403. Scheduled jobs and internal reversals stay unchanged.
>
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
