Connect Keycloack for Backend
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
The goal of the problem is to try and secure the backend with keycloak
How are you going to achieve the goal or solve the problem?
I will start and work on the problem and implement different ways until i find the right one.
What will be produced as a result of this effort and where will it live on GitLab?
As a result we are going to have a both a frontend and backend secured.
Give a justification of weight or due date.
Who will do it, and what will they do?
Migena Shkurti with people from other teams who are part of the IAM System in the same time.
What was the outcome?
After trying different ways we were able to secure the backend also. The new updated files are in the keycloak project for the reporting team.
Template Version 1.0.0
Edited by migena shkurti