Create endpoints to activate accounts after an user is registered

For the sake of security, add a proper CORS config to the project

Prepare the application to send e-mails, this will be useful when doing #29 and #28

Create all the flow to create, read, update and delete credit cards

Today we are using converter service from spring to convert DTO to model and vice-versa, the thing is: testing it is a bit hard and we don't need it now.

Remove the use of converter service and make use of pure interfaces with mapstruct to map between DTO and model.

Have better tests for the user account use case, this must be done to the controller and the service

Upgrade back-end to use new spring-boot v3

Look to the already done tests and improve it. The objective for this task is to have less duplicated code and create more parameterized tests

Create new endpoints to CRUD wallets:

• list
• create
• edit
• delete
• add integration and unit tests

If someone try to delete admin, the backend should bot permiti it since there will be no user able to login in the application, instead, it only permits locking it

Info endpoint should have free access without authentication

Refactor BE tests to make a good use of kotlin default parameters and named parameters

Add layered docker image build for BE

Some tests started to become a problem to maintain, to solve it a good approach might be:

• mock all tests done in the controller layer and let it check just the input of data (validation) and output (payload contents)
• in the service layer, integrate it with persistence layer and do a service to db and db to service check

In the future this will help when some complex scenario should be tested and starting from the controller might trigger a lot of services and the test could be easily bigger than the implementation

We should add a missing test about check if is possible to create debit cards

After updating detekt to v1.22 we need to update the rules

The toSpecification method in the filter DTO's is not good, it is using some parts of the infrastructure layer and those classes used there can be hidden by the repository since it should provide support for other classes that want's to query domain objects/entities

We should move it from there and put in a better place to have a good encapsulation of this query behavior.

Create all the flow to create, read, update and delete financial periods

Create all the flow to create, read, update and delete movement classes

SecurityConfiguration is using the WebSecurityConfigurerAdapter from spring, this class was deprecated in favor of another approach to configure the web security

The method on the endpoint to change the user password is not considering the future feature about making the password temporary.

We should add the flag there and later implement the rest of feature.

There is a missing test for the banking information validator in the wallet validators

Unique constraints are not created correctly for the tables, id and externalId should be separated unique constraints and not composite ones

All packages named as configuration should be renamed to administration

When creating a new wallet, bank information should be validated to guarantee that is unique if filled correctly

Add the user name and e-mail to the token response, this will be used to fill the user menu int the frontend

Some configs used by the project for building are deprecated on newer releases of Koltin

Review if the names of each schema are consistent with the menus on the UI

Now we can add a test to check if an already in use cost center is being deleted

Create endpoints to have a CRUD for users

• list
• create
• edit
• delete
• add integration and unit tests

Upgrade any possible libs

Today every time we need to use test containers, it starts and stops for every integration tests. There is better ways to work with the tool to make it run once and also improve the speed of our tests

We should remove UpdateSupport interface since we can do the mapping to update objects using mapstruct

Add to the user payloads and database the user preference for language

Update BE libs:

• Spring boot 3.1
• Kotlin 1.8.22

Spring has dreprecated WebSecurityConfigurerAdapter and the auth process seens not be consistent. We do really need redis?

The goal here is to review it beginning from the backend and look for improvements or pieces that can be removed to have a lighter auth process

Create the password recovery flow in the back-end, this should be done after the user CRUD is done

Spring boot 3 has provided support for the problem detail RFC in rest controllers, we should use it

Backend work for the cost centers CRUD:

• create endpoint to add
• create endpoint to edit
• create endpoint to find/list
• create automated tests (unit and integration)

It must extend the new interface to give support for updating fields in a PUT operation

Add english translation for the account activation e-mail

Pretty straight forward: upgrade backend libs to latest versions

A user with pending account activation can't be deleted because an error of data integrity violation, something related to the fact that this user is linked to the activation attempt.

Because of issue #47 from backend we discovered the fact that data integrity violations are not handled properly on the backend

API errors 404 are not using problem detail implementation like other errors should be using

Add tests for the token service and review the token controller tests to check if they are covering the basic usage

When a recover attempt is used with success the recover token is checked as used and should not be valid to get used again

Provide better naming to the tests to match their utility to the project

When a given JSON contains empty strings (not null, just "") the value for this string is not being translated to null value in the koltin code.