Planning vol. 2 Skip to content →

Planning vol. 2

This post is divided into two main parts. The technical part will be connected with adding custom headers passed to an authentication endpoint. In the second part, I’m going to describe plans for next few weeks.

I would like to remind you that all of the sources are available in my Github repository. Moreover, in the README file, you can find short project description with its main assumptions.

Forwarding headers

When our application relies on the REST, usually we must configure some custom headers that should be passed to a backend application. The most popular one is Authentication which is required to identify logged user. So far, all of the headers were hardcoded on the proxy’s side. Now, after adding some lines of code, a user is able to force the frontend module to pass custom headers to an authentication endpoint.

I added the map of headers to the ConfigurationDTO class:

In the AuthenticationRequestBuilder  class, those headers are added to headers passed to a HttpEntity object:

And honestly, that’s all did in the previous week…


… and I realized that it was time for next planning session. Akesi’s development became slow again. At the beginning, we should take a look for updated mindmap created in the Killing chaos and monotony.

Comparing to the previous map’s status, a few changes were made. “Frontend module” branch is completed. At the “proxy” branch only “production environment” and “management console” are left. Things from “production environment” are the last ones I want to do in the competition. Right now there is no sense in setting up Digital Ocean installation or publishing Docker images.

If no production, then the management console will be the next milestone. Due to lack of time, I’ll use well-known technologies: Spring + Angular (“typical Cracovian stack” as I heard once :D). All of the data will be stored in the file-based H2 database. More information I’ll provide later.