edk12564 opened a new pull request, #97: URL: https://github.com/apache/fineract-consumer-facing/pull/97
Issues: https://github.com/apache/fineract-consumer-facing/issues/87 # Summary Open banking was an important feature with a lot of interest. We should implement the start of openbanking infrastructure with the ability to act as a Spring Authorization Server to create open banking tokens. To start, we make sure to implement ES256 asymmetrical signing, JWTs, and openbanking endpoints to read User accounts. We also added functionality to revoke openbanking consent, and keep these consents/sessions in database for consistency across nodes. Next, we implemented a frontend login redirect for openbanking authentication, and a consent revocation option in the Profile feature. FInally as a side item, I noticed KYC could fall out of sync with Fineract, so KYC checks were added at token renewal for both login and openbanking tokens. If a user gets their KYC status revoked in Fineract, they will similarly get their access revoked in the BFF. ## More details - added Spring Authorization Server - implemented JDBC stateful tokens for consent/authorization checks - added openbanking scoped TPP tokens with refresh tokens and ES256 signatures - added KYC checks for each token refresh to keep BFF up to date with possible Fineract KYC revocations - added openbanking read endpoints for accounts and balances - added user consent revocation functionality - added Liquibase migrations for stateful openbanking tokens/consents - added consent approval page in frontend - added consent revocations to frontend - centralized code for kyc checks and frontend status badge styles -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
