Open leonardohscastilho opened 6 months ago
Previous Description:
This feature intends to generate this token based on a simple authentication method and provide a way to validate the generated token.
This feature should be implemented considering the following acceptance criteria points:
- The authentication method could be the simple Baerer user and password from the HTTP protocol since we are running under TLS.
- The password received should match the hash and salt saved on the user table. For it, bcrypt must be used.
- If the password matches, a jwt token should be generated and returned to the user.
- A function to validate if the token should be implemented as well.
- Unit test for all the implementation
We're missing the implementation of bank configuration API, the CDK was done here: https://github.com/in-fin-neat/in-fin-neat-cdk/pull/7 , it tells the IBAN is expected as a parameter of the endpoint
Bank config page in the UI was implemented here: https://github.com/in-fin-neat/infineat-ui/pull/2/
We are missing 1.iv, 3.i and 3.ii
User Story
As a cloud infineat user, I need to be able to configure my bank account details, so that other future infineat cloud functionalities can access it, as well as my current python cli can use it.
Acceptance Criteria
Tech Tasks
fetch_transactions
use these at the moment)Task blockers graph